-
Notifications
You must be signed in to change notification settings - Fork 25.5k
Document ILM waits for tsds end_time to lapse in some actions #100204
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
Documentation preview: |
Pinging @elastic/es-docs (Team:Docs) |
Pinging @elastic/es-data-management (Team:Data Management) |
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
- <<ilm-forcemerge>> | ||
- <<ilm-readonly>> | ||
- <<ilm-searchable-snapshot>> | ||
- <<ilm-shrink>> |
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.
and ilm-delete? (when other pr is merged)
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.
++ done, thanks Martijn
purposes is set to run after five minutes. | ||
takes place after the index is rolled over and the <<index-time-series-end-time, index time series end time>> | ||
has lapsed as the source index is still expected to receive writes until then. | ||
{ilm-cap} will not proceed with any action that expects the index to not receive |
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.
receive major writes? After end_time is passed a backing index can still accept writes, but the expectation is that the volume of writes will be lower.
💔 Backport failed
You can use sqren/backport to manually backport by running |
No description provided.