[DOC+] ILM min_age interpretation #98245
Merged
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
👋 hiya, team! From the time y'all helped me write this [ILM Troubleshooting blog](https://www.elastic.co/blog/troubleshooting-elasticsearch-ilm-common-issues-and-fixes) in 2021 and we later ported errors to [this doc](https://www.elastic.co/guide/en/elasticsearch/reference/master/index-lifecycle-error-handling.html) via #75849, the remaining top-gotcha user's raise is "Common issue 3" that ILM's `min_age` calculates off rollover time fallback index creation time. This PR cross-pollinates the blog quote into the docs so that Support can link it to users and so it becomes Google-able. > Common issue 3: min_age calculation clarification > When working with customers, I have seen confusion about how min_age works. The min_age must increase between subsequent phases. If rollover is used, min_age is calculated off the rollover date. This is because rollover generates a new index and the new index’s creation date is used in the calculation. Otherwise, min_age is calculated off the original index’s creation date.
stefnestor
added
>enhancement
>docs
|
Documentation preview: |
|
@stefnestor please enable the option "Allow edits and access to secrets by maintainers" on your PR. For more information, see the documentation. |
elasticsearchmachine
added
Team:Docs
|
Pinging @elastic/es-docs (Team:Docs) |
|
Pinging @elastic/es-data-management (Team:Data Management) |
abdonpijpelink
added
auto-backport-and-merge
abdonpijpelink
approved these changes
Aug 9, 2023
|
👋 @abdonpijpelink I see this is live in master but not 8.9 nor current, will you kindly help me backport/fix? |
|
I think it's after @abdonpijpelink's working hours. I'll work on backporting this. I think the |
💚 All backports created successfully
Questions ?Please refer to the Backport tool documentation |
jrodewig
added a commit
that referenced
this pull request
Aug 24, 2023
Co-authored-by: Abdon Pijpelink <abdon.pijpelink@elastic.co> Co-authored-by: Stef Nestor <26751266+stefnestor@users.noreply.github.com> fixes) in 2021 and we later ported errors to [this doc](https://www.elastic.co/guide/en/elasticsearch/reference/master/index-lifecycle-error-handling.html) via #75849, the remaining top-gotcha user's raise is "Common issue 3" that ILM's `min_age` calculates off rollover time fallback index creation time.
|
@stefnestor This is live on 8.9 and current now: https://www.elastic.co/guide/en/elasticsearch/reference/8.9/index-lifecycle-error-handling.html#_common_ilm_setting_issues |
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.
👋 hiya, team!
From the time y'all helped me write this ILM Troubleshooting blog in 2021 and @jrodewig later helped me port errors to this doc via #75849, the remaining top-gotcha user's are still encountering in EO2023 is "Common issue 3" that ILM's
min_agecalculates off rollover time fallback index creation time. (Users consistently expect this to only calculate from creation time.)This PR cross-pollinates the blog quote into the docs so that Support can link it to users and so it becomes Google-able.