[
https://issues.apache.org/jira/browse/ZOOKEEPER-1383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13205964#comment-13205964
]
Camille Fournier commented on ZOOKEEPER-1383:
---------------------------------------------
So, in short, I'm -1 on this until it stops breaking backwards compatibility.
Might consider adding the update throughput quotas separately from hard quota
limits.
> 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, 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
