Autoscaling reactive storage decider (#65520)#66236
Merged
henningandersen merged 1 commit intoelastic:7.xfrom Dec 14, 2020
Merged
Autoscaling reactive storage decider (#65520)#66236henningandersen merged 1 commit intoelastic:7.xfrom
henningandersen merged 1 commit intoelastic:7.xfrom
Conversation
The reactive storage decider will request additional capacity proportional to the size of shards that are either: * unassigned and unable to be allocated with only reason being storage on a node * shards that cannot remain where they are with only reason being storage and cannot be allocated anywhere else * shards that cannot remain where they are and cannot be allocated on any node and at least one node has storage as the only reason for unable to allocate. The reactive storage decider does not try to look into the future, thus at the time the reactive decider asks to scale up, the cluster is already in a need for more storage.
Collaborator
|
Pinging @elastic/es-distributed (Team:Distributed) |
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.
Backport of #65520
The reactive storage decider will request additional capacity
proportional to the size of shards that are either:
on a node
storage and cannot be allocated anywhere else
on any node and at least one node has storage as the only reason for
unable to allocate.
The reactive storage decider does not try to look into the future, thus
at the time the reactive decider asks to scale up, the cluster is
already in a need for more storage.