2014-04-02 00:28:08 +08:00
|
|
|
|
[[setup-upgrade]]
|
2019-03-14 05:38:13 +08:00
|
|
|
|
= Upgrade {es}
|
2017-12-06 02:58:52 +08:00
|
|
|
|
|
|
|
|
|
[partintro]
|
|
|
|
|
--
|
2019-03-14 05:38:13 +08:00
|
|
|
|
{es} can usually be upgraded using a <<rolling-upgrades,Rolling upgrade>>
|
|
|
|
|
process so upgrading does not interrupt service. Rolling upgrades are supported:
|
|
|
|
|
|
|
|
|
|
* Between minor versions
|
2019-07-02 15:06:14 +08:00
|
|
|
|
* From 5.6 to 6.8
|
2019-08-28 20:36:45 +08:00
|
|
|
|
* From 6.8 to {prev-major-version}
|
|
|
|
|
* From {prev-major-version} to {version}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The following table shows the recommended upgrade paths to {version}.
|
|
|
|
|
|
|
|
|
|
[cols="<1m,3",options="header",]
|
|
|
|
|
|====
|
|
|
|
|
|Upgrade from
|
|
|
|
|
|Recommended upgrade path to {version}
|
|
|
|
|
|
|
|
|
|
|{prev-major-version}
|
|
|
|
|
|<<rolling-upgrades,Rolling upgrade>> to {version}
|
|
|
|
|
|
|
|
|
|
|7.0–7.3
|
|
|
|
|
a|
|
|
|
|
|
. https://www.elastic.co/guide/en/elasticsearch/reference/{prev-major-version}/rolling-upgrades.html[Rolling upgrade] to {prev-major-version}
|
|
|
|
|
. <<rolling-upgrades,Rolling upgrade>> to {version}
|
|
|
|
|
|
|
|
|
|
|6.8
|
|
|
|
|
a|
|
|
|
|
|
. https://www.elastic.co/guide/en/elasticsearch/reference/{prev-major-version}/rolling-upgrades.html[Rolling upgrade] to {prev-major-version}
|
|
|
|
|
. <<rolling-upgrades,Rolling upgrade>> to {version}
|
|
|
|
|
|
|
|
|
|
|6.0–6.7
|
|
|
|
|
a|
|
|
|
|
|
|
|
|
|
|
. https://www.elastic.co/guide/en/elasticsearch/reference/6.8/rolling-upgrades.html[Rolling upgrade] to 6.8
|
|
|
|
|
. https://www.elastic.co/guide/en/elasticsearch/reference/{prev-major-version}/rolling-upgrades.html[Rolling upgrade] to {prev-major-version}
|
|
|
|
|
. <<rolling-upgrades,Rolling upgrade>> to {version}
|
|
|
|
|
|====
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
[WARNING]
|
|
|
|
|
====
|
|
|
|
|
The following upgrade paths are *not* supported:
|
|
|
|
|
|
|
|
|
|
* 6.8 to 7.0.
|
|
|
|
|
* 6.7 to 7.1.–{prev-major-version}.
|
|
|
|
|
====
|
2019-03-14 05:38:13 +08:00
|
|
|
|
|
|
|
|
|
{es} can read indices created in the previous major version. If you
|
|
|
|
|
have indices created in 5.x or before, you must reindex or delete them
|
|
|
|
|
before upgrading to {version}. {es} nodes will fail to start if
|
|
|
|
|
incompatible indices are present. Snapshots of 5.x or earlier indices cannot be
|
|
|
|
|
restored to a 7.x cluster even if they were created by a 6.x cluster. For
|
|
|
|
|
information about upgrading old indices, see <<reindex-upgrade, Reindex to upgrade>>.
|
|
|
|
|
|
|
|
|
|
When upgrading to a new version of {es}, you need to upgrade each
|
|
|
|
|
of the products in your Elastic Stack. For more information, see the
|
|
|
|
|
{stack-ref}/upgrading-elastic-stack.html[Elastic Stack Installation and Upgrade Guide].
|
|
|
|
|
|
|
|
|
|
To upgrade directly to {version} from 6.6 or earlier, you must shut down the
|
|
|
|
|
cluster, install {version}, and restart. For more information, see
|
|
|
|
|
<<restart-upgrade, Full cluster restart upgrade>>.
|
|
|
|
|
|
2017-12-06 02:58:52 +08:00
|
|
|
|
--
|
2016-10-11 18:14:35 +08:00
|
|
|
|
|
2017-08-24 05:03:14 +08:00
|
|
|
|
include::upgrade/rolling_upgrade.asciidoc[]
|
2014-04-02 00:28:08 +08:00
|
|
|
|
|
2017-08-24 05:03:14 +08:00
|
|
|
|
include::upgrade/cluster_restart.asciidoc[]
|
2016-10-11 18:14:35 +08:00
|
|
|
|
|
2017-12-15 16:42:36 +08:00
|
|
|
|
include::upgrade/reindex_upgrade.asciidoc[]
|