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

Fixes #23179 #23183

Merged
merged 1 commit into from
Sep 14, 2018
Merged

Fixes #23179 #23183

merged 1 commit into from
Sep 14, 2018

Conversation

programagor
Copy link
Contributor

Issue #23179 was caused by ignoring multiple replicas of the same shard, even if they are on different nodes. This commit fixes that.

Issue elastic#23179 was caused by ignoring multiple replicas of the same shard, even if they are on different nodes. This commit fixes that.
@elasticmachine
Copy link
Contributor

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?

@programagor
Copy link
Contributor Author

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.

@timroes
Copy link
Contributor

timroes commented Sep 14, 2018

Jenkins, test this

@timroes
Copy link
Contributor

timroes commented Sep 14, 2018

@chrisronline Can you have a look into this PR?

Copy link
Member

@pickypg pickypg left a 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!

@elasticmachine
Copy link
Contributor

💔 Build Failed

@pickypg
Copy link
Member

pickypg commented Sep 14, 2018

Please test this

@pickypg
Copy link
Member

pickypg commented Sep 14, 2018

(That's for our CI environment, not you; the first build failed because the server failed to start randomly)

Copy link
Contributor

@chrisronline chrisronline left a comment

Choose a reason for hiding this comment

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

LGTM too!

@elasticmachine
Copy link
Contributor

💚 Build Succeeded

@pickypg pickypg merged commit e2b304a into elastic:master Sep 14, 2018
pickypg pushed a commit that referenced this pull request Sep 14, 2018
Issue #23179 was caused by ignoring multiple replicas of the same shard, even if they are on different nodes. This commit fixes that.
pickypg pushed a commit that referenced this pull request Sep 14, 2018
Issue #23179 was caused by ignoring multiple replicas of the same shard, even if they are on different nodes. This commit fixes that.
@pickypg pickypg removed the v6.3.3 label Sep 14, 2018
@pickypg
Copy link
Member

pickypg commented Sep 14, 2018

6.x/6.5: 9183fe8
6.4: 529d7c4

This, surprisingly, did not backport cleanly to 6.3 so I chose to skip that.

@programagor programagor deleted the patch-1 branch September 14, 2018 16:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants