Skip to content

Commit 844616b

Browse files
[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.
1 parent 335eeeb commit 844616b

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

docs/reference/upgrade/rolling_upgrade.asciidoc

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -18,6 +18,12 @@ you can do a rolling upgrade you must encrypt the internode-communication with
1818
SSL/TLS, which requires a full cluster restart. For more information about this
1919
requirement and the associated bootstrap check, see <<bootstrap-checks-tls>>.
2020

21+
WARNING: The format used for the internal indices used by Kibana and {xpack}
22+
has changed in 6.x. When upgrading from 5.6 to 6.x, these internal indices have
23+
to be {stack-ref}/upgrading-elastic-stack.html#upgrade-internal-indices[upgraded]
24+
before the rolling upgrade procedure can start. Otherwise the upgraded node will
25+
refuse to join the cluster.
26+
2127
To perform a rolling upgrade:
2228

2329
. *Disable shard allocation*.

0 commit comments

Comments
 (0)