From 2f2ea0c280db993b79858ecffba4f076c5f94070 Mon Sep 17 00:00:00 2001 From: Clinton Gormley Date: Tue, 21 Jun 2016 18:02:55 +0200 Subject: [PATCH] Improved docs explaining the index upgrade process in breaking changes --- docs/reference/migration/migrate_5_0.asciidoc | 16 +++++++++------- 1 file changed, 9 insertions(+), 7 deletions(-) diff --git a/docs/reference/migration/migrate_5_0.asciidoc b/docs/reference/migration/migrate_5_0.asciidoc index 7dc79478c8a..da4ba2c521d 100644 --- a/docs/reference/migration/migrate_5_0.asciidoc +++ b/docs/reference/migration/migrate_5_0.asciidoc @@ -7,13 +7,9 @@ your application to Elasticsearch 5.0. [float] === Indices created before 5.0 -Elasticsearch 5.0 can read indices created in version 2.0 and above. If any -of your indices were created before 2.0 you will need to upgrade to the -latest 2.x version of Elasticsearch first, in order to upgrade your indices or -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. +Elasticsearch 5.0 can read indices created in version 2.0 or above. An +Elasticsearch 5.0 node will not start in the presence of indices created in a +version of Elasticsearch before 2.0. [IMPORTANT] .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 +<> 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] === Also see: