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

Before deleting a local unused shard copy, verify we're connected to the node it's supposed to be on #6191

Closed

Conversation

bleskes
Copy link
Contributor

@bleskes bleskes commented May 15, 2014

This is yet another safety guard to make sure we don't delete data if the local copy is the only one (even if it's not part of the cluster state any more)

…the node it's supposed to be on

This is yet another safety guard to make sure we don't delete data if the local copy is the only one (even if it's not part of the cluster state any more)
@s1monw
Copy link
Contributor

s1monw commented May 18, 2014

LGTM though - do we have the chance to get a test that reflects the problem or the reason we add this?

@bleskes bleskes added v1.3.0 and removed v1.2.0 labels May 18, 2014
@bleskes
Copy link
Contributor Author

bleskes commented May 18, 2014

@s1monw this is caused by a rare race condition in cluster state processing which the reason for infrequent failures on our feature/improve_zen branch. Writing a test that recreates it is failure hard. We try to keep that branch not to far from master which why I made the PR.

PS. I bumped the labels from 1.2.0 to 1.3.0 so there is no rush.

@s1monw
Copy link
Contributor

s1monw commented May 18, 2014

cool lets get this into 1.3 I agree a test is hard here.

@bleskes bleskes closed this in 05d131c May 20, 2014
@bleskes bleskes removed the review label May 20, 2014
bleskes added a commit that referenced this pull request May 20, 2014
…the node it's supposed to be on

This is yet another safety guard to make sure we don't delete data if the local copy is the only one (even if it's not part of the cluster state any more)

Closes #6191
@bleskes bleskes deleted the enhance/verify_connect_store_delete branch May 20, 2014 09:18
@clintongormley clintongormley changed the title Before deleting a local unused shard copy, verify we're connected to the node it's supposed to be on Resiliency: Before deleting a local unused shard copy, verify we're connected to the node it's supposed to be on Jul 16, 2014
@clintongormley clintongormley added the :Distributed/Recovery Anything around constructing a new shard, either from a local or a remote source. label Jun 7, 2015
@clintongormley clintongormley changed the title Resiliency: Before deleting a local unused shard copy, verify we're connected to the node it's supposed to be on Before deleting a local unused shard copy, verify we're connected to the node it's supposed to be on Jun 7, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Distributed/Recovery Anything around constructing a new shard, either from a local or a remote source. >enhancement resiliency v1.3.0 v2.0.0-beta1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants