[DOCS] Rolling upgrade with old internal indices #37184
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Pinging @elastic/es-docs |
lcawl
reviewed
Jan 7, 2019
| @@ -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} | |||
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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.
albertzaharovits
added a commit
that referenced
this pull request
Jan 9, 2019
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.
albertzaharovits
added a commit
that referenced
this pull request
Jan 9, 2019
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.
albertzaharovits
added a commit
that referenced
this pull request
Jan 9, 2019
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.
albertzaharovits
added a commit
that referenced
this pull request
Jan 9, 2019
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.
albertzaharovits
added a commit
that referenced
this pull request
Jan 9, 2019
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.
albertzaharovits
added a commit
that referenced
this pull request
Jan 9, 2019
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.
albertzaharovits
added a commit
that referenced
this pull request
Jan 9, 2019
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.
albertzaharovits
added a commit
that referenced
this pull request
Jan 9, 2019
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.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Closes #36984