Browse Source

[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.
Albert Zaharovits 6 years ago
parent
commit
4efbda1bc0
1 changed files with 6 additions and 0 deletions
  1. 6 0
      docs/reference/upgrade/rolling_upgrade.asciidoc

+ 6 - 0
docs/reference/upgrade/rolling_upgrade.asciidoc

@@ -18,6 +18,12 @@ you can do a rolling upgrade you must encrypt the internode-communication with
 SSL/TLS, which requires a full cluster restart. For more information about this
 requirement and the associated bootstrap check, see <<bootstrap-checks-tls>>.
 
+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*.