zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andor Molnar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ZOOKEEPER-3059) EventThread leak in case of Sasl AuthFailed
Date Tue, 19 Jun 2018 07:12:00 GMT

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-3059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16516731#comment-16516731
] 

Andor Molnar commented on ZOOKEEPER-3059:
-----------------------------------------

Of course, anytime [~abhishek.chouhan]

Sorry for the delayed feedback, I'm currently reviewing and trying your patch.

> 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
>            Priority: Critical
>              Labels: pull-request-available
>         Attachments: stack_dump
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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)

Mime
View raw message