[DOCS] disable the ILM history store on full cluster restore #88515
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
|
Pinging @elastic/es-docs (Team:Docs) |
dakrone
requested changes
Jul 13, 2022
Crikey! Good spot. I missed that even though I ctrl-f-ed for "start ILM" 😭 |
|
@elasticmachine update branch |
💔 Backport failedThe backport operation could not be completed due to the following error: You can use sqren/backport to manually backport by running |
andreidan
added
v8.6.1
auto-backport-and-merge
auto-backport
andreidan
added a commit
to andreidan/elasticsearch
that referenced
this pull request
Nov 24, 2022
…#88515) (cherry picked from commit 261f184) Signed-off-by: Andrei Dan <[email protected]>
andreidan
added a commit
that referenced
this pull request
Nov 24, 2022
…#91920) (cherry picked from commit 261f184) Signed-off-by: Andrei Dan <[email protected]>
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.
When restoring a full cluster there might be issues with the snapshot containing the
ilm-history data stream and, even though deleted from the elasticsearch cluster and ILM stopped, the history
data stream reappearing due to late processing of ILM history events.
This documents disabling the history index so that the data stream is not recreated and restoring
the snapshot doesn't fail due to the data stream already being present in the cluster.