zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From abhishek-chouhan <...@git.apache.org>
Subject [GitHub] zookeeper pull request #541: ZOOKEEPER-3059 EventThread leak in case of Sasl...
Date Sat, 23 Jun 2018 12:36:36 GMT
GitHub user abhishek-chouhan reopened a pull request:

    https://github.com/apache/zookeeper/pull/541

    ZOOKEEPER-3059 EventThread leak in case of Sasl AuthFailed

    Since authFailed is similar to session expired and is considered a fatal event, we should
clean up after ourselves once we get a AuthFailed, other wise this results in an unavoidable
and un-cleanable thread leak  of EventThread since the close operation is also a no-op (we
return after checking for isAlive).

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/abhishek-chouhan/zookeeper master

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/zookeeper/pull/541.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #541
    
----
commit c1d9d7afe1de246ad32d43032df7bb428fcceae6
Author: Abhishek Singh Chouhan <abhishekchouhan121@...>
Date:   2018-06-11T17:31:42Z

    ZOOKEEPER-3059 EventThread leak in case of Sasl AuthFailed

commit c54a83a486e4b6372e7004d44d2dbd0ba7ab61bb
Author: Abhishek Singh Chouhan <abhishekchouhan121@...>
Date:   2018-06-22T03:12:18Z

    ZOOKEEPER-3059 EventThread leak in case of Sasl AuthFailed. Adding testcase for the scenario

----


---

Mime
View raw message