Allow one search shard to fall back to undesired allocation #113847
Merged
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
pxsalehi
added
>non-issue
:Distributed Coordination/Allocation
elasticsearchmachine
added
serverless-linked
elasticsearchmachine
added
the
Team:Distributed (Obsolete)
|
Pinging @elastic/es-distributed (Team:Distributed) |
|
I think the approach is correct 👍 |
idegtiarenko
reviewed
Oct 1, 2024
...in/java/org/elasticsearch/cluster/routing/allocation/allocator/DesiredBalanceReconciler.java
Outdated
Show resolved
Hide resolved
It's in the linked test PR. To me it seemed we'd need |
idegtiarenko
approved these changes
Oct 1, 2024
matthewabbott
pushed a commit
to matthewabbott/elasticsearch
that referenced
this pull request
Oct 4, 2024
…113847) We allow a primary shard to be assigned to a node even if it is not its desired location, but not for replicas. With this change we allow at most one search shard to also fall back to allocation to an undesired nodes if necessary. This ensures that at least one search replica will be available even if the desired node cannot allocate it. Relates ES-9617
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.
We allow a primary shard to be assigned to a node even if it is not its desired location, but not for replicas. With this change we allow at most one search shard to also fall back to allocation to an undesired nodes if necessary. This ensures that at least one search replica will be available even if the desired node cannot allocate it.
Relates ES-9617