[
https://issues.apache.org/jira/browse/KAFKA-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15085300#comment-15085300
]
Flavio Junqueira commented on KAFKA-3038:
-----------------------------------------
You don't really need to batch with multi, you just need to make the calls
asynchronous. In fact, unless you really need to make multiple updates
transactional, the preferred way is to push updates asynchronously to keep the
pipeline full.
> 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
> Assignee: Eno Thereska
> Fix For: 0.9.0.0
>
>
> 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 message was sent by Atlassian JIRA
(v6.3.4#6332)
