[
https://issues.apache.org/jira/browse/KAFKA-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16101716#comment-16101716
]
ASF GitHub Bot commented on KAFKA-3038:
---------------------------------------
Github user resetius closed the pull request at:
https://github.com/apache/kafka/pull/2213
> 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.4.14#64029)
