Skip to content

[DOCS] Rolling upgrade with old internal indices #37184

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jan 9, 2019
Merged

[DOCS] Rolling upgrade with old internal indices #37184

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
456a259
Docs for rolling upgrade when internal indices
albertzaharovits Jan 7, 2019
4afd710
clarification
albertzaharovits Jan 7, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions docs/reference/upgrade/rolling_upgrade.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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}
Copy link
Contributor

@lcawl lcawl Jan 7, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In general, we're trying to get away from using "X-Pack" terminology. It hasn't been cleaned up everywhere yet, but if we can use something else here, that would be great. Would it be correct to say something like "the Elastic Stack commercial features" instead?

Copy link
Contributor Author

@albertzaharovits albertzaharovits Jan 8, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I am aware that the lingo had changed, but this is a warning message for users of 5.6 when X-Pack is still referred. Moreover, the proper stack upgrade docs in https://www.elastic.co/guide/en/elastic-stack/current/upgrading-elastic-stack.html, where the internal index upgrade step is described, still mention "X-Pack". I think using a different terminology would be confusing in this circumstance.

The decision is yours though, "The format used for the internal indices used by commercial features has changed in 6.x .", sounds equally fine to me.

Copy link
Contributor

@lcawl lcawl Jan 8, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You're right, I cleaned up some occurrences of X-Pack in that book yesterday, but there are still lots that seem relevant. This seems like one of those cases.

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*.
Expand Down