9caf354378
* [DOCS] Fixes titles in Setup section for consistency * [DOCS] Fixes to titles and orders of docs in Set up
89 lines
3.2 KiB
Plaintext
89 lines
3.2 KiB
Plaintext
[[upgrade]]
|
|
== Upgrade {kib}
|
|
|
|
Depending on the {kib} version you're upgrading from, the upgrade process to 7.0
|
|
varies.
|
|
|
|
NOTE: {kib} upgrades automatically when starting a new version, as described in
|
|
<<upgrade-migrations, this document>>.
|
|
Although you do not need to manually back up {kib} before upgrading, we recommend
|
|
that you have a backup on hand. You can use
|
|
<<snapshot-repositories, Snapshot and Restore>> to back up {kib}
|
|
data by targeting `.kibana*` indices. If you are using the Reporting plugin,
|
|
you can also target `.reporting*` indices.
|
|
|
|
[float]
|
|
[[upgrade-before-you-begin]]
|
|
=== Before you begin
|
|
|
|
Before you upgrade {kib}:
|
|
|
|
* Consult the <<breaking-changes,breaking changes>>.
|
|
* Before you upgrade production servers, test the upgrades in a dev environment.
|
|
* Back up your data with {es} {ref}/modules-snapshots.html[snapshots].
|
|
To roll back to an earlier version, you **must** have a backup of your data.
|
|
* If you are using custom plugins, check that a compatible version is
|
|
available.
|
|
* Shut down all {kib} nodes. Running more than one {kib} version against the
|
|
same Elasticseach index is unsupported. If you upgrade while older {kib} nodes are
|
|
running, the upgrade can fail.
|
|
|
|
To identify the changes you need to make to upgrade, and to enable you to
|
|
perform an Elasticsearch rolling upgrade with no downtime, you must upgrade to
|
|
6.7 before you upgrade to 7.0.
|
|
|
|
For a comprehensive overview of the upgrade process, refer to
|
|
*{stack-ref}/upgrading-elastic-stack.html[Upgrading the Elastic Stack]*.
|
|
|
|
|
|
[float]
|
|
[[upgrade-5x-earlier]]
|
|
=== Upgrade from 5.x or earlier
|
|
{es} can read indices created in the previous major version. Before you upgrade
|
|
to 7.0.0, you must reindex or delete any indices created in 5.x or earlier.
|
|
For more information, refer to
|
|
{stack-ref}/upgrading-elastic-stack.html#oss-stack-upgrade[Upgrading the Elastic Stack].
|
|
|
|
When your reindex is complete, follow the <<upgrade-standard, Standard upgrade>>
|
|
instructions.
|
|
|
|
[float]
|
|
[[upgrade-6x]]
|
|
=== Upgrade from 6.x
|
|
|
|
The recommended path is to upgrade to 6.8 before upgrading to 7.0. This makes it
|
|
easier to identify the required changes, and enables you to use the Upgrade
|
|
Assistant to prepare for your upgrade to 7.0.
|
|
|
|
TIP: The ability to import {kib} 6.x saved searches, visualizations, and
|
|
dashboards is supported.
|
|
|
|
[float]
|
|
[[upgrade-67]]
|
|
=== Upgrade from 6.8
|
|
To help you prepare for your upgrade to 7.0, 6.8 includes an https://www.elastic.co/guide/en/kibana/6.8/upgrade-assistant.html[Upgrade Assistant]
|
|
To access the assistant, go to *Management > 7.0 Upgrade Assistant*.
|
|
|
|
After you have addressed any issues that were identified by the Upgrade
|
|
Assistant, <<upgrade-standard,upgrade to 7.0>>.
|
|
|
|
[float]
|
|
=== Known issues
|
|
|
|
[float]
|
|
==== "shard failed" error when viewing {beats} dashboards in {kib}
|
|
After upgrading to {es} 7.0, any indices created by {beats} 6.6 or older will not
|
|
work in {kib} dashboards until the `index.query.default_field` setting is added
|
|
to each index. Indices created in {beats} 6.7 or later are unaffected.
|
|
To add the setting to the index, you can use the 7.0
|
|
{kibana-ref}/upgrade-assistant.html[Upgrade Assistant], or
|
|
//{beats-ref}/upgrading.html#dashboard-shard-failed[
|
|
add the setting manually
|
|
//]
|
|
.
|
|
|
|
|
|
include::upgrade/upgrade-standard.asciidoc[]
|
|
|
|
include::upgrade/upgrade-migrations.asciidoc[]
|