Notice regarding index.format in manual re-index steps (#14828)

This setting is not available until 5.6. Users are technically able to re-index against a previous version. If a user manually migrates their index without this setting and visits the Upgrade Assistant in 5.6, Kibana will still be shown as needing to be re-indexed, however it will fail with "Index .kibana-6 already exists. There may be an unfinished task reindexing to this index, or this index may have not been cleaned up previously."

Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>
This commit is contained in:
Tyler Smalley 2017-11-09 10:26:24 -08:00 committed by Tyler Smalley
parent 04c9b4d40b
commit e852b6300e

View file

@ -10,7 +10,7 @@ In order to migrate to Kibana 6, your Kibana index needs to be reindexed. This w
A UI is available in X-Pack 5.6 to assist with the migration. The following is provided should you be required to run the migration manually. The commands assume you're using the default `.kibana` index, without an alias. If `kibana.index` is set to something different in your `kibana.yml`, or you're using an alias, you will need to modify the commands.
To perform this migration without downtime, you will need to be running Kibana 5.6. This is the only version which supports both of the index types.
NOTE: To perform this migration without downtime, you will need to be running Kibana 5.6. This is the only version which supports both of the index types. If you are running a version prior to 5.6, you will need to remove `index.format` from the second step.
. Set `.kibana` index to read-only:
+