Details
-
Bug
-
Status: Resolved
-
Minor
-
Resolution: Duplicate
-
3.8.1
-
None
-
None
Description
The Java client sets a read timeout equal to 2/3 of the session timeout and throws a SessionTimeoutException when this is hit.
However, the effect of that exception is not treated the same was as a SessionExpiredException which is propagated to the user and is treated as a disconnect event instead.
This doesn't play very well with Curator which manages its own exception expiry client side and starts its countdown on disconnect events, meaning that it will consider the session lost a whole 2/3 of the session timeout after it actually expired.
Should the SessionTimeoutException also be propagated to the users for handling and potentially considering the session lost from their end?
Attachments
Issue Links
- duplicates
-
ZOOKEEPER-4508 ZooKeeper client run to endless loop in ClientCnxn.SendThread.run if all server down
- Patch Available