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

Hadoop QA commented on ZOOKEEPER-1383:
--------------------------------------

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12512700/ZOOKEEPER-1383.patch
  against trunk revision 1238176.

    +1 @author.  The patch does not contain any @author tags.

    +1 tests included.  The patch appears to include 15 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 appears to introduce 8 new Findbugs (version 1.3.9) 
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: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/935//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/935//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/935//console

This message is automatically generated.
                
> Create update throughput quotas and add hard quota limits
> ---------------------------------------------------------
>
>                 Key: ZOOKEEPER-1383
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1383
>             Project: ZooKeeper
>          Issue Type: New Feature
>          Components: server
>            Reporter: Jay Shrauner
>            Assignee: Jay Shrauner
>            Priority: Minor
>             Fix For: 3.5.0
>
>         Attachments: ZOOKEEPER-1383.patch
>
>
> Quotas exist for size (node count and size in bytes); it would be useful to 
> track and support quotas on update throughput (bytes per second) as well. 
> This can be tracked on both a node/subtree level for quota support as well as 
> on the server level for monitoring.
> In addition, the existing quotas log a warning when they are exceeded but 
> allow the transaction to proceed (soft quotas). It would also be useful to 
> support a corresponding set of hard quota limits that fail the transaction.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to