Details
-
Bug
-
Status: Closed
-
Critical
-
Resolution: Fixed
-
3.4.12
-
None
Description
In case of an authFailed sasl event we shutdown the send thread however we never close the event thread. Even if the client tries to close the connection it results in a no-op since we check for cnxn.getState().isAlive() which results in negative for auth failed state and we return without cleaning up. For applications that retry in case of auth failed by closing the existing connection and then trying to reconnect(eg. hbase replication) this eventually ends up exhausting the system resources.
Attachments
Attachments
Issue Links
- duplicates
-
ZOOKEEPER-2407 EventThread in ClientCnxn can't be closed when SendThread exits because of auth failed during reconnection
- Open
- links to
FAILURE: Integrated in Jenkins build ZooKeeper-trunk #74 (See https://builds.apache.org/job/ZooKeeper-trunk/74/)
ZOOKEEPER-3059: EventThread leak in case of Sasl AuthFailed (andor: rev 1fb644662b8e0530dec2c5668a3e49b3f614e9de)