Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Prefer primaries in cluster allocation explain #76220

Conversation

DaveCTurner
Copy link
Contributor

Today by default we explain the first unassigned shard in the routing
table. It's not unusual for this to be a replica which is unassigned
because its primary is also unassigned, which is not a helpful choice.
With this commit we explain the first unassigned primary if one exists,
falling back to the first unassigned replica if all primaries are
assigned.

Today by default we explain the first unassigned shard in the routing
table. It's not unusual for this to be a replica which is unassigned
because its primary is also unassigned, which is not a helpful choice.
With this commit we explain the first unassigned primary if one exists,
falling back to the first unassigned replica if all primaries are
assigned.
@DaveCTurner DaveCTurner added >enhancement :Distributed Coordination/Allocation All issues relating to the decision making around placing a shard (both master logic & on the nodes) v7.15.0 v8.0.0-alpha1 labels Aug 9, 2021
@DaveCTurner DaveCTurner requested a review from tlrx August 9, 2021 07:15
@elasticmachine elasticmachine added the Team:Distributed (Obsolete) Meta label for distributed team (obsolete). Replaced by Distributed Indexing/Coordination. label Aug 9, 2021
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-distributed (Team:Distributed)

Copy link
Member

@tlrx tlrx left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@DaveCTurner DaveCTurner merged commit 997441c into elastic:master Aug 9, 2021
@DaveCTurner DaveCTurner deleted the 2021-08-09-allocation-explain-prefer-primary branch August 9, 2021 11:45
DaveCTurner added a commit that referenced this pull request Aug 9, 2021
Today by default we explain the first unassigned shard in the routing
table. It's not unusual for this to be a replica which is unassigned
because its primary is also unassigned, which is not a helpful choice.
With this commit we explain the first unassigned primary if one exists,
falling back to the first unassigned replica if all primaries are
assigned.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Distributed Coordination/Allocation All issues relating to the decision making around placing a shard (both master logic & on the nodes) >enhancement Team:Distributed (Obsolete) Meta label for distributed team (obsolete). Replaced by Distributed Indexing/Coordination. v7.15.0 v8.0.0-alpha1 v8.0.0-alpha2
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants