-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
[DOCS] Document how to switch ILM policies #73967
Conversation
To switch an index's lifecycle policy, you must first remove the existing policy. Otherwise, phase execution for the index may silently fail. Closes #70151
Pinging @elastic/es-core-features (Team:Core/Features) |
Pinging @elastic/es-docs (Team:Docs) |
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 James, this LGTM.
Would it make sense to add a big warning that the remove policy API removes the policy (and all the ILM metadata) immediately without any consideration w.r.t where the index is in its lifecycle (mid-action executing for eg.) - it's the equivalent of kill -9
. As an example - it could happen that for an index that is in the forcemerge
action (a forcemerge action that changes the compression codec closes and reopens the index) after removing the policy using the API the index is closed.
So maybe besides a warning we should advise a manual/visual review of the index state before assigning a new policy?
Thanks @andreidan. I added a middle step to cover your suggestion. |
@elasticmachine run elasticsearch-ci/docs |
To switch an index's lifecycle policy, you must first remove the existing policy. Otherwise, phase execution for the index may silently fail.
Closes #70151
Preview