You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@zookeeper.apache.org by "Brian Nixon (JIRA)" <ji...@apache.org> on 2019/07/12 21:00:00 UTC

[jira] [Assigned] (ZOOKEEPER-3359) Batch commits in the CommitProcessor

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

Brian Nixon reassigned ZOOKEEPER-3359:
--------------------------------------

    Assignee: Brian Nixon

> Batch commits in the CommitProcessor
> ------------------------------------
>
>                 Key: ZOOKEEPER-3359
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3359
>             Project: ZooKeeper
>          Issue Type: Improvement
>          Components: quorum
>    Affects Versions: 3.6.0
>            Reporter: Brian Nixon
>            Assignee: Brian Nixon
>            Priority: Minor
>              Labels: pull-request-available
>          Time Spent: 2h 20m
>  Remaining Estimate: 0h
>
> Draining a single commit every time the CommitProcessor switches to commit mode can add to the backlog of committed messages. Instead, add controls to batch and drain multiple commits and limit the number of reads being served. Improves commit throughput and adds backpressure on reads.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)