[DOCS] ILM: Add ESS/ECE instructions for migrating to node roles #79742
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
elasticsearchmachine
added
v8.0.0
external-contributor
DanRoscigno
added
:Data Management/ILM+SLM
elasticmachine
added
Team:Data Management
|
Pinging @elastic/es-data-management (Team:Data Management) |
|
Pinging @elastic/es-docs (Team:Docs) |
debadair
reviewed
Oct 26, 2021
docs/reference/data-management/migrate-index-allocation-filters.asciidoc
Outdated
Show resolved
Hide resolved
docs/reference/data-management/migrate-index-allocation-filters.asciidoc
Outdated
Show resolved
Hide resolved
docs/reference/data-management/migrate-index-allocation-filters.asciidoc
Outdated
Show resolved
Hide resolved
docs/reference/data-management/migrate-index-allocation-filters.asciidoc
Outdated
Show resolved
Hide resolved
docs/reference/data-management/migrate-index-allocation-filters.asciidoc
Outdated
Show resolved
Hide resolved
docs/reference/data-management/migrate-index-allocation-filters.asciidoc
Outdated
Show resolved
Hide resolved
docs/reference/data-management/migrate-index-allocation-filters.asciidoc
Outdated
Show resolved
Hide resolved
…s.asciidoc Co-authored-by: debadair <[email protected]>
…s.asciidoc Co-authored-by: debadair <[email protected]>
…s.asciidoc Co-authored-by: debadair <[email protected]>
…s.asciidoc Co-authored-by: debadair <[email protected]>
…s.asciidoc Co-authored-by: debadair <[email protected]>
…s.asciidoc Co-authored-by: debadair <[email protected]>
|
Feedback from @mduarte : For version <= 7.10 and < 7.14 Adding a warm, cold or frozen tier, as well as enabling autocaling will migrate the deployment from node_type to node_roles. For versions >= 7.14 All of the above is true, plus: It also migrates to node_roles on upgrade to a version >= 7.14 |
jrodewig
changed the title
jrodewig
approved these changes
Oct 28, 2021
There was a problem hiding this comment.
Thanks @DanRoscigno. This LGTM.
I left Deb's suggestions as is with the exception of a minor typo. Aside from that typo, the other comments and suggestions are non-blocking. Feel free to disregard them if wanted.
Let me know when you're ready to publish this. I can handle the merge + backports for you.
docs/reference/data-management/migrate-index-allocation-filters.asciidoc
Outdated
Show resolved
Hide resolved
docs/reference/data-management/migrate-index-allocation-filters.asciidoc
Outdated
Show resolved
Hide resolved
docs/reference/data-management/migrate-index-allocation-filters.asciidoc
Outdated
Show resolved
Hide resolved
docs/reference/data-management/migrate-index-allocation-filters.asciidoc
Outdated
Show resolved
Hide resolved
docs/reference/data-management/migrate-index-allocation-filters.asciidoc
Outdated
Show resolved
Hide resolved
docs/reference/data-management/migrate-index-allocation-filters.asciidoc
Outdated
Show resolved
Hide resolved
docs/reference/data-management/migrate-index-allocation-filters.asciidoc
Outdated
Show resolved
Hide resolved
Co-authored-by: James Rodewig <[email protected]>
…s.asciidoc Co-authored-by: James Rodewig <[email protected]>
Co-authored-by: James Rodewig <[email protected]>
Co-authored-by: James Rodewig <[email protected]>
Co-authored-by: James Rodewig <[email protected]>
DanRoscigno
commented
Oct 28, 2021
docs/reference/data-management/migrate-index-allocation-filters.asciidoc
Outdated
Show resolved
Hide resolved
DanRoscigno
commented
Oct 28, 2021
docs/reference/data-management/migrate-index-allocation-filters.asciidoc
Outdated
Show resolved
Hide resolved
jrodewig
reviewed
Oct 28, 2021
docs/reference/data-management/migrate-index-allocation-filters.asciidoc
Outdated
Show resolved
Hide resolved
Co-authored-by: James Rodewig <[email protected]>
|
@jrodewig can you give me more info on adding a lead-in sentence to the self managed section (the unresolved comment up above). Here is a new screenshot from a build: |
|
Hey @DanRoscigno! This looks good. By "lead-in sentence" I meant "To switch to using node roles:", and you've already re-added that. |
This was referenced Oct 28, 2021
elasticsearchmachine
pushed a commit
that referenced
this pull request
Oct 28, 2021
) (#80045) Adds documentation informing the reader about how the Elasticsearch Service / Elastic Cloud Enterprise upgrade process and autoscaling system automate the migration of the Elasticsearch nodes and ILM policies to using node.roles rather than filtering on node attributes. Co-authored-by: debadair <[email protected]> Co-authored-by: James Rodewig <[email protected]> Co-authored-by: Dan Roscigno <[email protected]> Co-authored-by: debadair <[email protected]>
elasticsearchmachine
pushed a commit
that referenced
this pull request
Oct 28, 2021
) (#80047) Adds documentation informing the reader about how the Elasticsearch Service / Elastic Cloud Enterprise upgrade process and autoscaling system automate the migration of the Elasticsearch nodes and ILM policies to using node.roles rather than filtering on node attributes. Co-authored-by: debadair <[email protected]> Co-authored-by: James Rodewig <[email protected]> Co-authored-by: Dan Roscigno <[email protected]> Co-authored-by: debadair <[email protected]>
elasticsearchmachine
pushed a commit
that referenced
this pull request
Oct 28, 2021
) (#80046) Adds documentation informing the reader about how the Elasticsearch Service / Elastic Cloud Enterprise upgrade process and autoscaling system automate the migration of the Elasticsearch nodes and ILM policies to using node.roles rather than filtering on node attributes. Co-authored-by: debadair <[email protected]> Co-authored-by: James Rodewig <[email protected]> Co-authored-by: Dan Roscigno <[email protected]> Co-authored-by: debadair <[email protected]>
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.
This PR adds documentation informing the reader about how the Elasticsearch Service / Elastic Cloud Enterprise upgrade process and autoscaling system automate the migration of the Elasticsearch nodes and ILM policies to using node.roles rather than filtering on node attributes.
Upgrading from Stack 7.7 to 7.15 in both Elasticsearch Service and Elastic Cloud Enterprise was tested, both with and without allowing the upgrade to automatically migrate to node roles. Both environments were also tested with and without autoscaling. Finally, a non-default index template which included the use of node attributes was tested with @stefnestor . All of the test scenarios passed.
Here is a screenshot highlighting the changes (updated with feedback from Deb and Mario):
