Improved docs explaining the index upgrade process in breaking changes
This commit is contained in:
parent
6177c0a900
commit
2f2ea0c280
|
@ -7,13 +7,9 @@ your application to Elasticsearch 5.0.
|
||||||
[float]
|
[float]
|
||||||
=== Indices created before 5.0
|
=== Indices created before 5.0
|
||||||
|
|
||||||
Elasticsearch 5.0 can read indices created in version 2.0 and above. If any
|
Elasticsearch 5.0 can read indices created in version 2.0 or above. An
|
||||||
of your indices were created before 2.0 you will need to upgrade to the
|
Elasticsearch 5.0 node will not start in the presence of indices created in a
|
||||||
latest 2.x version of Elasticsearch first, in order to upgrade your indices or
|
version of Elasticsearch before 2.0.
|
||||||
to delete the old indices. Elasticsearch will not start in the presence of old
|
|
||||||
indices. To upgrade 2.x indices, first start a node which have access to all
|
|
||||||
the data folders and let it upgrade all the indices before starting up rest of
|
|
||||||
the cluster.
|
|
||||||
|
|
||||||
[IMPORTANT]
|
[IMPORTANT]
|
||||||
.Reindex indices from Elasticseach 1.x or before
|
.Reindex indices from Elasticseach 1.x or before
|
||||||
|
@ -26,6 +22,12 @@ way to do this is to upgrade to Elasticsearch 2.3 or later and to use the
|
||||||
|
|
||||||
=========================================
|
=========================================
|
||||||
|
|
||||||
|
The first time Elasticsearch 5.0 starts, it will automatically rename index
|
||||||
|
folders to use the index UUID instead of the index name. If you are using
|
||||||
|
<<indices-shadow-replicas,shadow replicas>> with shared data folders, first
|
||||||
|
start a single node with access to all data folders, and let it rename all
|
||||||
|
index folders before starting other nodes in the cluster.
|
||||||
|
|
||||||
[float]
|
[float]
|
||||||
=== Also see:
|
=== Also see:
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue