You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: