[Doc] Update instructions for 7.0 upgrade #10621
Closed
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
|
@lcawl Tagging you as requested. |
16 tasks
karenzone
commented
Apr 1, 2019
docs/static/upgrading.asciidoc
Outdated
| in the Elastic Stack upgrade guide, Logstash 7.0 should not be upgraded before Elasticsearch 7.0. This is both | ||
| practical and because some Logstash 7.0 plugins may attempt to use features of Elasticsearch 7.0 that did not exist | ||
| in earlier versions. For example, if you attempt to send the 7.x template to a cluster before Elasticsearch 7.0, then | ||
| all indexing will fail likely fail. If you use your own custom template with Logstash, | ||
| then this issue can be ignored. | ||
|
|
||
| Note the Elasticsearch Output Index Template change in the <<breaking-changes>> documentation for further insight into |
There was a problem hiding this comment.
At line 165, does the note about Output Index Template breaking change come out for 7.0?
There was a problem hiding this comment.
I suppose, if the user upgraded via 6.7 then they might have read this Note
|
@guyboertje or @jsvd Can you take a look, please? We'll likely need to make more changes, but I'd like to get this merged for stack upgrade testing. |
elasticsearch-bot
pushed a commit
that referenced
this pull request
Apr 3, 2019
elasticsearch-bot
pushed a commit
that referenced
this pull request
Apr 3, 2019
elasticsearch-bot
pushed a commit
that referenced
this pull request
Apr 3, 2019
elasticsearch-bot
pushed a commit
that referenced
this pull request
Apr 3, 2019
elasticsearch-bot
pushed a commit
that referenced
this pull request
Apr 3, 2019
elasticsearch-bot
pushed a commit
that referenced
this pull request
Apr 3, 2019
elasticsearch-bot
pushed a commit
that referenced
this pull request
Apr 3, 2019
elasticsearch-bot
pushed a commit
that referenced
this pull request
Apr 3, 2019
|
@guyboertje Thank you! Iteration continues starting now. |
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.
Updated instructions for 7.0 upgrade. Added format/info on PQ upgrade info pre- and post-6.3.
I have not tested/verified these instructions at this time. This PR is to get the framework and versions in place.