Allocation awareness allocates some replicas #104800
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
The docs for forced awareness indicate that no replicas will be assigned until all zones are available, which is definitely undesirable and also not the actual behaviour. This commit fixes the wording to match what really happens. Closes elastic#104777
DaveCTurner
added
>docs
|
Documentation preview: |
elasticsearchmachine
added
the
Team:Distributed (Obsolete)
|
Pinging @elastic/es-docs (Team:Docs) |
|
Pinging @elastic/es-distributed (Team:Distributed) |
toughcoding
reviewed
Jan 28, 2024
| from allocating replicas if only one zone is available: | ||
| For example, if you have an awareness attribute called `zone` and configure | ||
| nodes in `zone1` and `zone2`, you can use forced awareness to make {es} leave | ||
| half of your shard copies unassigned if only one zone is available: |
There was a problem hiding this comment.
Can we use "replica shards" instead of "shard copies" word?
There was a problem hiding this comment.
No, I mean shard copies, i.e. replicas and primaries.
idegtiarenko
approved these changes
Jan 29, 2024
DaveCTurner
deleted the
2024/01/26/allocation-awareness-allocates-some-replicas
branch
DaveCTurner
added a commit
that referenced
this pull request
Jan 29, 2024
The docs for forced awareness indicate that no replicas will be assigned until all zones are available, which is definitely undesirable and also not the actual behaviour. This commit fixes the wording to match what really happens. Closes #104777
DaveCTurner
added a commit
that referenced
this pull request
Jan 29, 2024
The docs for forced awareness indicate that no replicas will be assigned until all zones are available, which is definitely undesirable and also not the actual behaviour. This commit fixes the wording to match what really happens. Closes #104777
DaveCTurner
restored the
2024/01/26/allocation-awareness-allocates-some-replicas
branch
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.
The docs for forced awareness indicate that no replicas will be assigned
until all zones are available, which is definitely undesirable and also
not the actual behaviour. This commit fixes the wording to match what
really happens.
Closes #104777