[+DOC][ILM] age calculation resets post rollover #103662
Merged
Conversation
This file contains hidden or 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
👋 howdy, team! I have the internal belief/understanding that [ILM Explain](https://www.elastic.co/guide/en/elasticsearch/reference/current/ilm-explain-lifecycle.html)'s `age` calculates based off rollover time fall back index creation time (or ILM creation time override settings). However, I'm not able to find that currently in existing docs, so adding it to [ILM > Phase Transitions](https://www.elastic.co/guide/en/elasticsearch/reference/8.11/ilm-index-lifecycle.html#ilm-phase-transitions) Background: This relates to > ([doc](https://www.elastic.co/guide/en/elasticsearch/reference/current/getting-started-index-lifecycle-management.html#ilm-gs-check-progress)) The `age` of the indexed used to transition to the next phase (in this case it is the same with the age of the index). Uh... I'm not actually(/currently) finding an official Elastic doc confirming `age` works off index creation time override to rollover time, but I know that's correspondingly true from the blog I wrote that LeeH had signed-off > ([blog](https://www.elastic.co/blog/troubleshooting-elasticsearch-ilm-common-issues-and-fixes)) **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](https://www.elastic.co/guide/en/elasticsearch/reference/current/ilm-index-lifecycle.html#ilm-phase-transitions) 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. We're working to tighten-ship on docs+api for users to self-service understanding > (internal link) The `age` of an index is calculated based on: > - The `index_creation_date_millis` of the index IF it did not go through `hot.rollover` > - The rollover time of the index (TODO: `time_since_index_rollover`) IF it went through `hot.rollover` (noting rollover resets `age`) > - Index ILM Setting overrides `index.lifecycle.origination_date` or `index.lifecycle.parse_origination_date` (related [blog](https://www.elastic.co/blog/control-ilm-phase-transition-timings-using-origination-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. |
|
Pinging @elastic/es-docs (Team:Docs) |
elasticsearchmachine
added
v8.11.4
external-contributor
|
Pinging @elastic/es-data-management (Team:Data Management) |
Co-authored-by: Lee Hinman <dakrone@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
👋 howdy, team!
I have the internal belief/understanding that ILM Explain's
agecalculates based off rollover time fall back index creation time (or ILM creation time override settings). However, I'm not able to find that currently in existing docs, so adding it to ILM > Phase Transitions. (Also adding column name references for doc searchability.)TIA!
Background
This surfaced from:
Uh... I'm not actually(/currently) finding an official Elastic doc confirming
ageworks off index creation time override to rollover time, but I know that's correspondingly true from the blog I wrote that LeeH had signed-offWe're working to tighten-ship on docs+api for users to self-service understanding
Related: #103660, #103659