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

Don't delete local shard data when its allocated on a node that doesn't exists #4502

Closed
kimchy opened this Issue Dec 18, 2013 · 0 comments

Comments

Projects
None yet
1 participant
@kimchy
Member

kimchy commented Dec 18, 2013

This is an extreme case, exposed by a bug we had in our allocation in local gateway, causing a cluster state that doesn't include a node in the nodes list, but still has the shard in the routing table pointing at the non existent node. Then, when a node on the same box comes back, it will cause the local shard data to be deleted because it thinks its fully allocated on other nodes.

@kimchy kimchy closed this in f0356b2 Dec 18, 2013

kimchy added a commit that referenced this issue Dec 18, 2013

Don't delete local shard data when its allocated on a node that doesn…
…'t exists

This is an extreme case, exposed by a bug we had in our allocation in local gateway, causing a cluster state that doesn't include a node in the nodes list, but still has the shard in the routing table pointing at the non existent node. Then, when a node on the same box comes back, it will cause the local shard data to be deleted because it thinks its fully allocated on other nodes.
fixes #4502

brusic added a commit to brusic/elasticsearch that referenced this issue Jan 19, 2014

Don't delete local shard data when its allocated on a node that doesn…
…'t exists

This is an extreme case, exposed by a bug we had in our allocation in local gateway, causing a cluster state that doesn't include a node in the nodes list, but still has the shard in the routing table pointing at the non existent node. Then, when a node on the same box comes back, it will cause the local shard data to be deleted because it thinks its fully allocated on other nodes.
fixes #4502

mute pushed a commit to mute/elasticsearch that referenced this issue Jul 29, 2015

Don't delete local shard data when its allocated on a node that doesn…
…'t exists

This is an extreme case, exposed by a bug we had in our allocation in local gateway, causing a cluster state that doesn't include a node in the nodes list, but still has the shard in the routing table pointing at the non existent node. Then, when a node on the same box comes back, it will cause the local shard data to be deleted because it thinks its fully allocated on other nodes.
fixes #4502
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment