[
https://issues.apache.org/jira/browse/ZOOKEEPER-4412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kezhu Wang resolved ZOOKEEPER-4412.
-----------------------------------
Resolution: Duplicate
ZooKeeper client will dead loop in case it could not reach any of the servers
from connection string. It only learn session expiration from server side. So,
I guess servers in connection string crashed long time ago before them come
back. I am going to close this as ZOOKEEPER-4508 introduces client side session
expiration to break the dead loop.
> client blocked too long before session timeout
> ----------------------------------------------
>
> Key: ZOOKEEPER-4412
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-4412
> Project: ZooKeeper
> Issue Type: Bug
> Components: java client
> Affects Versions: 3.4.14
> Reporter: tian
> Priority: Critical
>
> set Negotiated session timeout: 40000
> I have thousands of zk clients under a zk cluster, when switch failure, some
> of clients did not send suspend event to state listner after 204988ms, but
> indeed session was expired in server as expected in server after 40000ms
> {code:java}
> // code placeholder
> [10.10.10.2][my-app][2021-11-05 13:55:38.701][
> WARN][????][16.195.152:2181)][o.a.z.ClientCnxn ] :
> [][][]Client session timed out, have not heard from server in 204988ms for
> sessionid 0x405005d85480c3d
> [10.10.10.2][my-app][2021-10-30 15:55:39.275][
> WARN][????][16.195.152:218)][o.a.z.ClientCnxn ] :
> [][][]Unable to reconnect to ZooKeeper service, session 0x405005d85480c3d has
> expired
> [10.10.10.2][my-app][2021-10-30 15:55:39.275][
> WARN][????][ain-EventThread][o.a.c.ConnectionState ] :
> [][][]Session expired event received{code}
> why after {color:#ff0000}204988ms this client found client session timeout ?
> socket read timeout = 2/3 * sessiont time out , it blocked too long to
> discover network failure. what may cause this scene?{color}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
