[ https://issues.apache.org/jira/browse/ZOOKEEPER-831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12895440#action_12895440 ]
Hadoop QA commented on ZOOKEEPER-831: ------------------------------------- +1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12451268/ZOOKEEPER-831.patch against trunk revision 980576. +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-h7.grid.sp2.yahoo.net/107/testReport/ Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Zookeeper-Patch-h7.grid.sp2.yahoo.net/107/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Console output: http://hudson.zones.apache.org/hudson/job/Zookeeper-Patch-h7.grid.sp2.yahoo.net/107/console This message is automatically generated. > BookKeeper: Throttling improved for reads > ----------------------------------------- > > Key: ZOOKEEPER-831 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-831 > Project: Zookeeper > Issue Type: Bug > Components: contrib-bookkeeper > Affects Versions: 3.3.1 > Reporter: Flavio Junqueira > Assignee: Flavio Junqueira > Fix For: 3.4.0 > > Attachments: ZOOKEEPER-831.patch > > > Reads and writes in BookKeeper are asymmetric: a write request writes one > entry, whereas a read request may read multiple requests. The current > implementation of throttling only counts the number of read requests instead > of counting the number of entries being read. Consequently, a few read > requests reading a large number of entries each will spawn a large number of > read-entry requests. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.