[
https://issues.apache.org/jira/browse/ZOOKEEPER-1093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13068056#comment-13068056
]
Patrick Hunt commented on ZOOKEEPER-1093:
-----------------------------------------
I'd like to see this go into 3.4.0, I'm assuming that it's not possible to test
(easily -- see testBadPeerAddressInQuorum if you want to try). Is the code
exercised, what could we look at in the console output to verify?
> ZooKeeper quotas will always trigger if set on one criteria but not the other
> ------------------------------------------------------------------------------
>
> Key: ZOOKEEPER-1093
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1093
> Project: ZooKeeper
> Issue Type: Bug
> Components: server
> Affects Versions: 3.3.3, 3.4.0
> Reporter: Camille Fournier
> Assignee: Camille Fournier
> Attachments: ZOOKEEPER-1093.patch
>
>
> /testing has quota on bytes but not node count. Count quota will always fire
> because it is set to -1 and will always fail comparison.
> 2011-06-13 16:01:53,492 - WARN [CommitProcessor:3:DataTree@373] - Quota
> exceeded: /testing count=4 limit=-1
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
