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

Allocation awareness does not respect allocation excludes #52374

Open
DaveCTurner opened this issue Feb 14, 2020 · 1 comment
Open

Allocation awareness does not respect allocation excludes #52374

DaveCTurner opened this issue Feb 14, 2020 · 1 comment

Comments

@DaveCTurner
Copy link
Contributor

@DaveCTurner DaveCTurner commented Feb 14, 2020

Today if you are using allocation awareness and you wish to decommission an entire zone, you may not be able to gracefully vacate all shards from this zone since allocation awareness computes the maximum number of shards per zone without regard for any allocation filters, and these constraints may conflict.

We will address this with #49064, but we may like to consider having allocation awareness respect certain cluster-wide allocation exclusions too, as a special case to support zone-wide vacation. We saw one case where this might have been useful recently, so I'm opening this to collect other evidence that this would be useful.

Relates #8178, #49064.

@elasticmachine

This comment has been minimized.

Copy link
Collaborator

@elasticmachine elasticmachine commented Feb 14, 2020

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.