[
https://issues.apache.org/jira/browse/ZOOKEEPER-3793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated ZOOKEEPER-3793:
--------------------------------------
Labels: pull-request-available (was: )
> Request throttling is broken when RequestThrottler is disabled or configured
> incorrectly.
> -----------------------------------------------------------------------------------------
>
> Key: ZOOKEEPER-3793
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3793
> Project: ZooKeeper
> Issue Type: Bug
> Components: server
> Affects Versions: 3.6.0
> Reporter: Michael Han
> Assignee: Michael Han
> Priority: Critical
> Labels: pull-request-available
>
> When RequestThrottler is not enabled or is enabled but configured
> incorrectly, ZooKeeper server will stop throttling. This is a serious bug as
> without request throttling, it's fairly easy to overwhelm ZooKeeper which
> leads to all sorts of issues.
> This is a regression introduced in ZOOKEEPER-3243, where the total number of
> queued requests in request processing pipeline is not taking into
> consideration when deciding whether to throttle or not, or only taken into
> consideration conditionally based on RequestThrottler's configurations. We
> should make sure always taking into account the number of queued requests in
> request processing pipeline before making throttling decisions.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
