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

Clusterstate misses the cluster name as it's identifier #5622

Closed
s1monw opened this Issue Mar 31, 2014 · 0 comments

Comments

Projects
None yet
1 participant
@s1monw
Copy link
Contributor

s1monw commented Mar 31, 2014

Today the cluster_state is not associated with the cluster_name which is odd since it's pretty much it's only valid identifier. Any node can send a cluster state to another node today even if it's not the same cluster. These situations can happen rarely during tests or even in the wild by accident. The problem can occur if multiple nodes run on the same machine and they join multiple clusters. If node A from cluster cluster_name=a shuts down while the other node B starts up with cluster_name=b and this node happens to get the same port on that physical host a third node that still thinks B is listening on that port might send a new cluster state. This can cause weird problems and we should discard the cluster state if the cluster names don't match

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.