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
We have a service using this node-zookeeper-client lib to connect to a multi-host zookeeper cluster. When the zookeeper cluster has massive traffic, within one minute after the client successfully connects to the zk cluster, the new session becomes EXPIRED. It's confirmed by the zookeeper server log.
My questions are:
Is this expected to see such frequent session EXPIRED when there is massive traffic in the zookeeper cluster? (ps. we have other services talking to the same zk cluster, but none of them experiences the same issue)
Since the zk-client-session becomes "EXPIRED" state (and according to the zookeeper document, EXPIRED state is not a recoverable state), is restarting my service, which will re-create a new zk-client-session, the recommended approach?
The text was updated successfully, but these errors were encountered:
sliu2013
changed the title
Constantly getting "onSocketError" when zookeeper cluster has massive traffic
Constantly getting EXPIRED session when zookeeper cluster has massive traffic
Apr 22, 2021
We have a service using this node-zookeeper-client lib to connect to a multi-host zookeeper cluster. When the zookeeper cluster has massive traffic, within one minute after the client successfully connects to the zk cluster, the new session becomes EXPIRED. It's confirmed by the zookeeper server log.
My questions are:
The text was updated successfully, but these errors were encountered: