-
Notifications
You must be signed in to change notification settings - Fork 25k
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
Ensure autoexpand keeps shards on remaining nodes #119829
base: main
Are you sure you want to change the base?
Ensure autoexpand keeps shards on remaining nodes #119829
Conversation
Adding a test that ensures that during node replacement autoexpand removes a shard from node to be shutdown (and not any other node) and adds a new one to the replacement node.
Pinging @elastic/es-distributed-coordination (Team:Distributed Coordination) |
@@ -405,6 +412,75 @@ private void assertThatAutoExpandReplicasDidNotContract(IndexMetadata indexMetad | |||
); | |||
} | |||
|
|||
public void testShouldKeepAllShardOnRemainingNodes() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why not an IT?
@@ -207,6 +215,51 @@ public void testAutoExpandDuringNodeReplacement() { | |||
); | |||
} | |||
|
|||
@AwaitsFix(bugUrl = "https://github.com/elastic/elasticsearch/issues/119843") | |||
public void testShouldKeepAllShardOnRemainingNodes() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I find it odd to introduces a test that is muted. IMO, this belongs to a PR that also includes a fix.
Adding a test that ensures that during node replacement autoexpand
removes a shard from node to be shutdown (and not any other node)
and adds a new one to the replacement node.