- Notifications
You must be signed in to change notification settings - Fork 25.5k
remove index.lifecycle.skip setting #34823
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
With the introduction of _ilm/stop and _ilm/start APIs, the use cases where one would only target a select group of indices to start/stop has been reduced. Since there is no strong use-case for skipping specific indices, it is best to remove this functionality and only adding if later desired, with the hopes of keeping things more simple.
Pinging @elastic/es-core-infra |
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.
LGTM if CI passes
thanks for the review @colings86. 🤞 |
test this please |
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.
LGTM too, assuming CI is green.
One note: https://github.com/elastic/elasticsearch/blob/index-lifecycle/x-pack/docs/en/ilm/pause-resume-ilm.asciidoc still mentions that "ILM can be skipped on a per-index basis", but since that isn't actual documentation yet it's probably fine. This doc is changed in your other PR, ignore this 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.
In case it wasn't clear I meant to approve this rather than just comment.
test this please |
With the introduction of _ilm/stop and _ilm/start APIs, the use cases where one would only target a select group of indices to start/stop has been reduced. Since there is no strong use-case for skipping specific indices, it is best to remove this functionality and only adding if later desired, with the hopes of keeping things more simple.
We want to be able to skip specific indices in ILM again for elastic#109206. This is essentially just a revert of elastic#34823.
We want to be able to skip specific indices in ILM again for elastic#109206. This is essentially just a revert of elastic#34823. (cherry picked from commit 269fbbc) # Conflicts: # server/src/main/java/org/elasticsearch/TransportVersions.java
With the introduction of _ilm/stop and _ilm/start APIs, the
use cases where one would only target a select group
of indices to start/stop has been reduced. Since there is no
strong use-case for skipping specific indices, it is best to
remove this functionality and only adding if later desired, with the
hopes of keeping things more simple.