You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Edward Carter (JIRA)" <ji...@apache.org> on 2014/06/03 00:23:03 UTC

[jira] [Updated] (ZOOKEEPER-1928) add configurable throttling to the number of snapshots concurrently sent by a leader

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

Edward Carter updated ZOOKEEPER-1928:
-------------------------------------

    Attachment: ZOOKEEPER-1928.patch

> add configurable throttling to the number of snapshots concurrently sent by a leader
> ------------------------------------------------------------------------------------
>
>                 Key: ZOOKEEPER-1928
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1928
>             Project: ZooKeeper
>          Issue Type: Improvement
>          Components: server
>            Reporter: Edward Carter
>            Assignee: Edward Carter
>         Attachments: ZOOKEEPER-1928.patch, ZOOKEEPER-1928.patch, ZOOKEEPER-1928.patch
>
>   Original Estimate: 168h
>  Remaining Estimate: 168h
>
> We want to add configurable throttling to the number of snapshots concurrently sent by a leader.  Without this, when recovering from a partial outage or network partition, the leader can become overloaded and unresponsive due to its attempts to send snapshots to too many followers and observers all at once.  The throttle will operate by terminating the connection of any observer receiving a snapshot deemed to be in excess of the throttle.  Followers should be allowed to receive snapshots unconditionally, though those snapshots do count against the quota.
> I have a patch ready which implements this.



--
This message was sent by Atlassian JIRA
(v6.2#6252)