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

Posted to dev@kafka.apache.org by "Ismael Juma (JIRA)" <ji...@apache.org> on 2017/03/02 13:36:45 UTC

[jira] [Updated] (KAFKA-3038) Speeding up partition reassignment after broker failure

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

Ismael Juma updated KAFKA-3038:
-------------------------------
    Fix Version/s:     (was: 0.11.0.0)

> Speeding up partition reassignment after broker failure
> -------------------------------------------------------
>
>                 Key: KAFKA-3038
>                 URL: https://issues.apache.org/jira/browse/KAFKA-3038
>             Project: Kafka
>          Issue Type: Improvement
>          Components: controller, core
>    Affects Versions: 0.9.0.0
>            Reporter: Eno Thereska
>
> After a broker failure the controller does several writes to Zookeeper for each partition on the failed broker. Writes are done one at a time, in closed loop, which is slow especially under high latency networks. Zookeeper has support for batching operations (the "multi" API). It is expected that substituting serial writes with batched ones should reduce failure handling time by an order of magnitude.
> This is identified as an issue in https://cwiki.apache.org/confluence/display/KAFKA/kafka+Detailed+Replication+Design+V3 (section End-to-end latency during a broker failure)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)