You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@zookeeper.apache.org by "Abhishek Singh Chouhan (JIRA)" <ji...@apache.org> on 2018/06/11 17:22:00 UTC

[jira] [Created] (ZOOKEEPER-3059) EventThread leak in case of Sasl AuthFailed

Abhishek Singh Chouhan created ZOOKEEPER-3059:
-------------------------------------------------

             Summary: EventThread leak in case of Sasl AuthFailed
                 Key: ZOOKEEPER-3059
                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3059
             Project: ZooKeeper
          Issue Type: Bug
    Affects Versions: 3.4.12
            Reporter: Abhishek Singh Chouhan
            Assignee: Abhishek Singh Chouhan
         Attachments: stack_dump

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.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)