-
Notifications
You must be signed in to change notification settings - Fork 25.7k
[+DOC] Restore policies in restoring ILM indices #90119
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.
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
Conversation
👋 howdy! This may need Asciidoc reformatting. Will you kindly add in express commentary on [Restore a managed Datastream or Index](https://www.elastic.co/guide/en/elasticsearch/reference/master/index-lifecycle-and-snapshots.html?edit) to also restore ILM policies as needed (via `include_global_state`). Otherwise, you induce ILM errors once ILM starts (and have to do a form of repeating the entire outlined procedure to get indices going through correctly.)
|
Documentation preview: |
|
@stefnestor please enable the option "Allow edits and access to secrets by maintainers" on your PR. For more information, see the documentation. |
|
Pinging @elastic/es-docs (Team:Docs) |
abdonpijpelink
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for adding this note @stefnestor ! I think we should maybe open with this recommendation? I've reworded a bit, and fixed the broken link. Let me know what you think.
Co-authored-by: Abdon Pijpelink <[email protected]>
|
Sounds great. Thanks for the feedback @abdonpijpelink ! |
|
@elasticmachine update branch |
💚 Backport successful
|
* [+DOC] Restore policies in restoring ILM indices 👋 howdy! This may need Asciidoc reformatting. Will you kindly add in express commentary on [Restore a managed Datastream or Index](https://www.elastic.co/guide/en/elasticsearch/reference/master/index-lifecycle-and-snapshots.html?edit) to also restore ILM policies as needed (via `include_global_state`). Otherwise, you induce ILM errors once ILM starts (and have to do a form of repeating the entire outlined procedure to get indices going through correctly.) * Apply suggestions from code review Co-authored-by: Abdon Pijpelink <[email protected]> Co-authored-by: Abdon Pijpelink <[email protected]> Co-authored-by: Elastic Machine <[email protected]>
* [+DOC] Restore policies in restoring ILM indices 👋 howdy! This may need Asciidoc reformatting. Will you kindly add in express commentary on [Restore a managed Datastream or Index](https://www.elastic.co/guide/en/elasticsearch/reference/master/index-lifecycle-and-snapshots.html?edit) to also restore ILM policies as needed (via `include_global_state`). Otherwise, you induce ILM errors once ILM starts (and have to do a form of repeating the entire outlined procedure to get indices going through correctly.) * Apply suggestions from code review Co-authored-by: Abdon Pijpelink <[email protected]> Co-authored-by: Abdon Pijpelink <[email protected]> Co-authored-by: Elastic Machine <[email protected]> Co-authored-by: Abdon Pijpelink <[email protected]> Co-authored-by: Elastic Machine <[email protected]>
👋 howdy! This may need Asciidoc reformatting. Will you kindly add in express commentary on Restore a managed Datastream or Index to also restore ILM policies as needed (via
include_global_state, related doc). Otherwise, you induce ILM errors once ILM starts (and have to do a form of repeating the entire outlined procedure to get indices going through correctly.)