Skip to content

Only auto-expand replicas with allocation filtering when all nodes upgraded #50361

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

Merged
merged 4 commits into from
Dec 20, 2019

Conversation

ywelsch
Copy link
Contributor

@ywelsch ywelsch commented Dec 19, 2019

Follow-up to #48974 that ensures that replicas are only auto-expanded according to allocation filtering rules once all nodes are upgraded to a version that supports this. Helps with orchestrating cluster upgrades.

@ywelsch ywelsch added >non-issue :Distributed Coordination/Allocation All issues relating to the decision making around placing a shard (both master logic & on the nodes) v8.0.0 v7.6.0 labels Dec 19, 2019
@ywelsch ywelsch requested a review from DaveCTurner December 19, 2019 11:09
@elasticmachine
Copy link
Collaborator

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

@ywelsch ywelsch removed the request for review from DaveCTurner December 19, 2019 11:19
@ywelsch ywelsch requested a review from DaveCTurner December 19, 2019 13:13
@ywelsch
Copy link
Contributor Author

ywelsch commented Dec 19, 2019

@elasticmachine run elasticsearch-ci/2

Copy link
Contributor

@DaveCTurner DaveCTurner left a comment

Choose a reason for hiding this comment

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

LGTM

@ywelsch ywelsch merged commit e6d2b29 into elastic:master Dec 20, 2019
ywelsch added a commit that referenced this pull request Dec 20, 2019
…graded (#50361)

Follow-up to #48974 that ensures that replicas are only auto-expanded according to allocation
filtering rules once all nodes are upgraded to a version that supports this. Helps with
orchestrating cluster upgrades.
ywelsch added a commit that referenced this pull request Dec 20, 2019
ywelsch added a commit that referenced this pull request Dec 20, 2019
Follow-up to #50361 that fixes the test that does not work against older ES versions
ywelsch added a commit that referenced this pull request Dec 20, 2019
…graded (#50361)

Follow-up to #48974 that ensures that replicas are only auto-expanded according to allocation
filtering rules once all nodes are upgraded to a version that supports this. Helps with
orchestrating cluster upgrades.
ywelsch added a commit that referenced this pull request Dec 20, 2019
Follow-up to #50361 that fixes the test that does not work against older ES versions
SivagurunathanV pushed a commit to SivagurunathanV/elasticsearch that referenced this pull request Jan 23, 2020
…graded (elastic#50361)

Follow-up to elastic#48974 that ensures that replicas are only auto-expanded according to allocation
filtering rules once all nodes are upgraded to a version that supports this. Helps with
orchestrating cluster upgrades.
SivagurunathanV pushed a commit to SivagurunathanV/elasticsearch that referenced this pull request Jan 23, 2020
Follow-up to elastic#50361 that fixes the test that does not work against older ES versions
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) >non-issue v7.6.0 v8.0.0-alpha1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants