zookeeper-dev mailing list archives

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

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

Hudson commented on ZOOKEEPER-3059:

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)
* (edit) src/java/main/org/apache/zookeeper/ClientCnxn.java
* (edit) src/java/test/org/apache/zookeeper/SaslAuthTest.java

> 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
>             Fix For: 3.6.0, 3.5.5
>         Attachments: stack_dump
>          Time Spent: 2h 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

View raw message