From f9346b868ba5aee68dddfd8e1ab549030f070f73 Mon Sep 17 00:00:00 2001 From: Albert Zaharovits Date: Wed, 9 Jan 2019 18:14:22 +0200 Subject: [PATCH] [DOCS] Rolling upgrade with old internal indices (#37184) Upgrading the Elastic Stack perfectly documents the process to upgrade ES from 5 to 6 when internal indices are present. However, the rolling upgrade docs do not mention anything about internal indices. This adds a warning in the rolling upgrade procedure, highlighting that internal indices should be upgraded before the rolling upgrade procedure can be started. --- docs/reference/upgrade/rolling_upgrade.asciidoc | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/reference/upgrade/rolling_upgrade.asciidoc b/docs/reference/upgrade/rolling_upgrade.asciidoc index d38f2dcff55ef..fdb70ad334897 100644 --- a/docs/reference/upgrade/rolling_upgrade.asciidoc +++ b/docs/reference/upgrade/rolling_upgrade.asciidoc @@ -19,6 +19,12 @@ SSL/TLS, which requires a full cluster restart. For more information about this requirement and the associated bootstrap check, see {ref}/bootstrap-checks-xpack.html#bootstrap-checks-tls[SSL/TLS check]. +WARNING: The format used for the internal indices used by Kibana and {xpack} +has changed in 6.x. When upgrading from 5.6 to 6.x, these internal indices have +to be {stack-ref}/upgrading-elastic-stack.html#upgrade-internal-indices[upgraded] +before the rolling upgrade procedure can start. Otherwise the upgraded node will +refuse to join the cluster. + To perform a rolling upgrade: . *Disable shard allocation*.