[7.x] ILM use Priority.IMMEDIATE for stop ILM cluster update (#54909)#55018
Merged
andreidan merged 2 commits intoelastic:7.xfrom Apr 11, 2020
Merged
Conversation
This changes the priority of the cluster state update that stops ILM altogether to `IMMEDIATE`. We've chosen to change this as it can be useful to temporarily stop ILM if a cluster is overwhelmed, but a `NORMAL` priority can see the "stop ILM update" not make it up the tasks queue. On the same note, we're keeping the `start ILM` cluster update priority to `NORMAL` on purpose such that we only start `ILM` if the cluster can handle it. (cherry picked from commit d67df3a) Signed-off-by: Andrei Dan <andrei.dan@elastic.co>
Collaborator
|
Pinging @elastic/es-core-features (:Core/Features/ILM+SLM) |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
This changes the priority of the cluster state update that stops ILM
altogether to
IMMEDIATE. We've chosen to change this as it can be useful totemporarily stop ILM if a cluster is overwhelmed, but a
NORMALpriority can see the "stop ILM update" not make it up the tasks queue.
On the same note, we're keeping the
start ILMcluster update priorityto
NORMALon purpose such that we only startILMif the cluster canhandle it.
(cherry picked from commit d67df3a)
Signed-off-by: Andrei Dan andrei.dan@elastic.co
Backport of #54909