[
https://issues.apache.org/jira/browse/BOOKKEEPER-999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sijie Guo resolved BOOKKEEPER-999.
----------------------------------
Resolution: Fixed
Fix Version/s: 4.5.0
Issue resolved by merging pull request 105
[https://github.com/apache/bookkeeper/pull/105]
{noformat}
commit 32ebf0ad68f85daffdec571e28206339a4d09443
Author: Robert (Bobby) Evans <[email protected]>
AuthorDate: Wed Mar 22 16:51:48 2017 -0700
Commit: Sijie Guo <[email protected]>
CommitDate: Wed Mar 22 16:51:48 2017 -0700
BOOKKEEPER-999: Stop leaking threads in BookKeeper client
Author: Robert (Bobby) Evans <[email protected]>
Reviewers: Sijie Guo <[email protected]>, Enrico Olivelli
<[email protected]>, Jia Zhai <[email protected]>, Kai S <None>,
Venkateswararao Jujjuri (JV) <None>
Closes #105 from revans2/BOOKKEEPER-999
{noformat}
> BookKeeper client can leak threads
> ----------------------------------
>
> Key: BOOKKEEPER-999
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-999
> Project: Bookkeeper
> Issue Type: Bug
> Components: bookkeeper-client
> Affects Versions: 4.4.0
> Reporter: Robert Joseph Evans
> Assignee: Robert Joseph Evans
> Fix For: 4.5.0
>
>
> The client constructor
> {{BookKeeper(ClientConfiguration conf, ZooKeeper zk)}}
> in 4.4 and above will create a new NioClientSocketChannelFactory but does not
> set the ownership of that factory to true so threads are leaked.
> This showed up as a failure in BookieRecoveryTest on MacOS where it has a
> hard coded limit of about 2000 threads in a single process, and this test was
> going beyond that.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
