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

ZooKeeper may think a node is dead before the node realizes #6

Open
pron opened this issue Jul 9, 2012 · 1 comment
Open

ZooKeeper may think a node is dead before the node realizes #6

pron opened this issue Jul 9, 2012 · 1 comment
Assignees
Labels

Comments

@pron
Copy link
Contributor

pron commented Jul 9, 2012

If ZK thinks a node is dead, the information may not spread to the cluster at once. The server may think the node has died and start serving its items to other nodes who've noticed the death, while the node itself thinks it's still alive and continue serving nodes that also think it's alive.

@ghost ghost assigned pron Jul 9, 2012
@pron
Copy link
Contributor Author

pron commented Jul 9, 2012

Verifying with ZK that you're alive before serving other nodes' requests is impractical.
What we should do, is set the ZK connection timeout on the client (node) to be less than that of the ZK timeout for determining node death, so the node itself will actually be more conservative and think it's dead (thus stop serving requests) before other nodes realize it. This OK, because eventually they all will.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants