-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Fixes #23179 #23183
Fixes #23179 #23183
Conversation
Issue elastic#23179 was caused by ignoring multiple replicas of the same shard, even if they are on different nodes. This commit fixes that.
Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually? |
As a note, this does not reintroduce #19704, since that issue resulted in the same replica being visible multiple times on the same node, which this PR still catches successfully. It just allows multiple copies of a replica to be on different nodes. |
Jenkins, test this |
@chrisronline Can you have a look into this PR? |
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.
LGTM.
This is a good spotting and good fix. Thanks!
💔 Build Failed |
Please test this |
(That's for our CI environment, not you; the first build failed because the server failed to start randomly) |
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.
LGTM too!
💚 Build Succeeded |
Issue #23179 was caused by ignoring multiple replicas of the same shard, even if they are on different nodes. This commit fixes that.
Issue #23179 was caused by ignoring multiple replicas of the same shard, even if they are on different nodes. This commit fixes that.
Issue #23179 was caused by ignoring multiple replicas of the same shard, even if they are on different nodes. This commit fixes that.