You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@zookeeper.apache.org by "Michael Han (Jira)" <ji...@apache.org> on 2019/09/16 21:27:00 UTC

[jira] [Resolved] (ZOOKEEPER-3503) Add server side large request throttling

     [ https://issues.apache.org/jira/browse/ZOOKEEPER-3503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Han resolved ZOOKEEPER-3503.
------------------------------------
    Fix Version/s: 3.6.0
       Resolution: Fixed

Issue resolved by pull request 1051
[https://github.com/apache/zookeeper/pull/1051]

> Add server side large request throttling
> ----------------------------------------
>
>                 Key: ZOOKEEPER-3503
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3503
>             Project: ZooKeeper
>          Issue Type: Improvement
>          Components: server
>    Affects Versions: 3.6.0
>            Reporter: Jie Huang
>            Priority: Minor
>              Labels: pull-request-available
>             Fix For: 3.6.0
>
>          Time Spent: 1h 50m
>  Remaining Estimate: 0h
>
> This task adds a new request limiting mechanism to ZooKeeper that aims to protect ZooKeeper from accepting too many large requests and crashing because it runs out of memory. This is designed to augment the connection throttling (ZOOKEEPER-3242) and request throttling (ZOOKEEPER-3243), which focus on limiting the number rather than size of requests.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)