[ https://issues.apache.org/jira/browse/ZOOKEEPER-373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12699828#action_12699828 ]
Hadoop QA commented on ZOOKEEPER-373: ------------------------------------- +1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12405634/ZOOKEEPER-373.patch against trunk revision 764673. +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 3 new or modified tests. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 findbugs. The patch does not introduce any new Findbugs warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. +1 core tests. The patch passed core unit tests. +1 contrib tests. The patch passed contrib unit tests. Test results: http://hudson.zones.apache.org/hudson/job/Zookeeper-Patch-vesta.apache.org/34/testReport/ Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Zookeeper-Patch-vesta.apache.org/34/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Console output: http://hudson.zones.apache.org/hudson/job/Zookeeper-Patch-vesta.apache.org/34/console This message is automatically generated. > One thread per bookie > --------------------- > > Key: ZOOKEEPER-373 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-373 > Project: Zookeeper > Issue Type: Improvement > Components: contrib-bookkeeper > Affects Versions: 3.1.1 > Reporter: Flavio Paiva Junqueira > Assignee: Flavio Paiva Junqueira > Fix For: 3.2.0 > > Attachments: ZOOKEEPER-373.patch, ZOOKEEPER-373.patch, > ZOOKEEPER-373.patch > > > Currently, if a client is writing to multiple ledgers and these ledgers > overlap on some bookie, there will be as many threads for such a bookie as > the number of ledgers writing to it. Consequently, if a client writes to many > ledgers simultaneously, it may end up with an undesirably large number of > threads. I don't have a concrete proposal yet, but I suspect it is as simple > as keeping an array of BookieHandle objects, one per bookie, and having each > BookieHandle object shared by all ledgers. > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.