[DOC] Add ILM errors & gotchas #75849
Assignees
Labels
:Data Management/ILM+SLM
Index and Snapshot lifecycle management
>docs
General docs changes
Team:Data Management
Meta label for data/management team
Team:Docs
Meta label for docs team
Comments
|
Pinging @elastic/es-docs (Team:Docs) |
|
Thanks @stefnestor. Tagging @debadair, who structured most of our ILM docs. She'll have the best idea of where to slot this content in. |
jrodewig
added
the
:Data Management/ILM+SLM
elasticmachine
added
the
Team:Data Management
|
Pinging @elastic/es-core-features (Team:Core/Features) |
|
I think we can add this as a "Common policy execution issues" section in the "error handling" topic: https://www.elastic.co/guide/en/elasticsearch/reference/7.13/index-lifecycle-error-handling.html @jrodewig @lockewritesdocs We've been trending toward having Troubleshooting sections with this sort of info. Should we rename this topic to align with that? |
That sounds great to me. Thanks! |
Definitely makes sense! As these pages grow and contain information for multiple issues, Troubleshooting feels like the best way to group things. |
debadair
added a commit
to debadair/elasticsearch
that referenced
this issue
Aug 26, 2021
debadair
added a commit
to debadair/elasticsearch
that referenced
this issue
Aug 26, 2021
…tic#76957) * [DOCS] Add ILM error/troubleshooting info. Closes elastic#75849 * Apply suggestions from code review Co-authored-by: James Rodewig <40268737+jrodewig@users.noreply.github.com> * Updated xref & fixed whitespace issues Co-authored-by: James Rodewig <40268737+jrodewig@users.noreply.github.com>
debadair
added a commit
to debadair/elasticsearch
that referenced
this issue
Aug 26, 2021
…tic#76957) * [DOCS] Add ILM error/troubleshooting info. Closes elastic#75849 * Apply suggestions from code review Co-authored-by: James Rodewig <40268737+jrodewig@users.noreply.github.com> * Updated xref & fixed whitespace issues Co-authored-by: James Rodewig <40268737+jrodewig@users.noreply.github.com>
debadair
added a commit
to debadair/elasticsearch
that referenced
this issue
Aug 26, 2021
…tic#76957) * [DOCS] Add ILM error/troubleshooting info. Closes elastic#75849 * Apply suggestions from code review Co-authored-by: James Rodewig <40268737+jrodewig@users.noreply.github.com> * Updated xref & fixed whitespace issues Co-authored-by: James Rodewig <40268737+jrodewig@users.noreply.github.com>
debadair
added a commit
to debadair/elasticsearch
that referenced
this issue
Aug 31, 2021
…tic#76957) * [DOCS] Add ILM error/troubleshooting info. Closes elastic#75849 * Apply suggestions from code review Co-authored-by: James Rodewig <40268737+jrodewig@users.noreply.github.com> * Updated xref & fixed whitespace issues Co-authored-by: James Rodewig <40268737+jrodewig@users.noreply.github.com>
debadair
added a commit
to debadair/elasticsearch
that referenced
this issue
Aug 31, 2021
…tic#76957) * [DOCS] Add ILM error/troubleshooting info. Closes elastic#75849 * Apply suggestions from code review Co-authored-by: James Rodewig <40268737+jrodewig@users.noreply.github.com> * Updated xref & fixed whitespace issues Co-authored-by: James Rodewig <40268737+jrodewig@users.noreply.github.com>
debadair
added a commit
to debadair/elasticsearch
that referenced
this issue
Aug 31, 2021
…tic#76957) * [DOCS] Add ILM error/troubleshooting info. Closes elastic#75849 * Apply suggestions from code review Co-authored-by: James Rodewig <40268737+jrodewig@users.noreply.github.com> * Updated xref & fixed whitespace issues Co-authored-by: James Rodewig <40268737+jrodewig@users.noreply.github.com>
This was referenced Aug 31, 2021
debadair
added a commit
that referenced
this issue
Sep 1, 2021
…7095) * [DOCS] Add ILM error/troubleshooting info. Closes #75849 * Apply suggestions from code review Co-authored-by: James Rodewig <40268737+jrodewig@users.noreply.github.com> * Updated xref & fixed whitespace issues Co-authored-by: James Rodewig <40268737+jrodewig@users.noreply.github.com> Co-authored-by: James Rodewig <40268737+jrodewig@users.noreply.github.com>
debadair
added a commit
that referenced
this issue
Sep 1, 2021
…7094) * [DOCS] Add ILM error/troubleshooting info. Closes #75849 * Apply suggestions from code review Co-authored-by: James Rodewig <40268737+jrodewig@users.noreply.github.com> * Updated xref & fixed whitespace issues Co-authored-by: James Rodewig <40268737+jrodewig@users.noreply.github.com> Co-authored-by: James Rodewig <40268737+jrodewig@users.noreply.github.com>
debadair
added a commit
that referenced
this issue
Sep 1, 2021
…7093) * [DOCS] Add ILM error/troubleshooting info. Closes #75849 * Apply suggestions from code review Co-authored-by: James Rodewig <40268737+jrodewig@users.noreply.github.com> * Updated xref & fixed whitespace issues Co-authored-by: James Rodewig <40268737+jrodewig@users.noreply.github.com> Co-authored-by: James Rodewig <40268737+jrodewig@users.noreply.github.com>
stefnestor
added a commit
that referenced
this issue
Aug 6, 2023
👋 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.
abdonpijpelink
added a commit
that referenced
this issue
Aug 9, 2023
* [DOC+] ILM min_age interpretation 👋 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. * Apply suggestions from code review --------- Co-authored-by: Abdon Pijpelink <abdon.pijpelink@elastic.co>
jrodewig
added a commit
that referenced
this issue
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.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@jrodewig cross-posting now live blog: https://www.elastic.co/blog/troubleshooting-elasticsearch-ilm-common-issues-and-fixes. In particular, add "Common issues" section w/info (pre-approved in blog go-live process by @dakrone)
The text was updated successfully, but these errors were encountered: