Skip to content

Latest commit

 

History

History
65 lines (54 loc) · 3.24 KB

upgrade-standard.asciidoc

File metadata and controls

65 lines (54 loc) · 3.24 KB
Raw

Standard upgrade

Note
 7.17 includes an Upgrade Assistant to help you prepare for your upgrade to 8.0. To access the assistant, go to Stack Management > Upgrade Assistant.
Important

If you’ve saved and/or exported objects in {kib} that rely on the Elasticsearch Query DSL, make sure to check the {es} {ref}/breaking-changes.html[breaking changes] documentation and take the necessary remediation steps as per those instructions.

Upgrading multiple {kib} instances

Note
 Kibana does not support rolling upgrades. If you’re running multiple {kib} instances, all instances should be stopped before upgrading.

Different versions of {kib} running against the same {es} index, such as during a rolling upgrade, can cause data loss. This is because older instances will continue to write saved objects in a different format than the newer instances. To prevent this from happening ensure that all old {kib} instances are shutdown before starting up instances on a newer version.

Upgrade using a deb or rpm package

  1. Stop the existing {kib} process using the appropriate command for your system. If you have multiple {kib} instances connecting to the same {es} cluster ensure that all instances are stopped before proceeding to the next step to avoid data loss.

  2. Use rpm or dpkg to install the new package. All files should be placed in their proper locations and config files should not be overwritten.

    Make sure you remove or update any configurations that are indicated in the breaking changes documentation otherwise {kib} will fail to start.

  1. Upgrade any plugins by removing the existing plugin and reinstalling the appropriate version using the kibana-plugin script. Check out the plugins documentation for more information.

  2. Start the new {kib} process using the appropriate command for your system.

Upgrade using a zip or tar.gz archive

  1. Extract the zip or tar.gz archive to a new directory to be sure that you don’t overwrite the config or data directories.

Important
 If you use {monitor-features}, you must re-use the data directory when you upgrade {kib}. Otherwise, the {kib} instance is assigned a new persistent UUID and becomes a new instance in the monitoring data.

  1. Copy the files from the config directory from your old installation to your new installation. Make sure you remove or update any configurations that are indicated in the breaking changes documentation otherwise {kib} will fail to start.

  2. Copy the files from the data directory from your old installation to your new installation.

  3. Install the appropriate versions of all your plugins for your new installation using the kibana-plugin script. Check out the plugins documentation for more information.

  4. Stop the old {kib} process. If you have multiple {kib} instances connecting to the same {es} cluster ensure that all instances are stopped before proceeding to the next step to avoid data loss.

  5. Start the new {kib} process.