[
https://issues.apache.org/jira/browse/KAFKA-5501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16101244#comment-16101244
]
Ismael Juma commented on KAFKA-5501:
------------------------------------
The merged PR adds the async ZookeeperClient, but it doesn't include the
changes to use said client. [~onurkaraman], I reopened, but perhaps we should
repurpose his JIRA and create new ones for using the APIs. Probably one for the
controller, one for the authorizer, one for configs, etc. Does that make sense?
> use async zookeeper apis everywhere
> -----------------------------------
>
> Key: KAFKA-5501
> URL: https://issues.apache.org/jira/browse/KAFKA-5501
> Project: Kafka
> Issue Type: Sub-task
> Reporter: Onur Karaman
> Assignee: Onur Karaman
> Fix For: 1.0.0
>
>
> Synchronous zookeeper writes means that we wait an entire round trip before
> doing the next write. These synchronous writes are happening at a
> per-partition granularity in several places, so partition-heavy clusters
> suffer from the controller doing many sequential round trips to zookeeper.
> * PartitionStateMachine.electLeaderForPartition updates leaderAndIsr in
> zookeeper on transition to OnlinePartition. This gets triggered per-partition
> sequentially with synchronous writes during controlled shutdown of the
> shutting down broker's replicas for which it is the leader.
> * ReplicaStateMachine updates leaderAndIsr in zookeeper on transition to
> OfflineReplica when calling KafkaController.removeReplicaFromIsr. This gets
> triggered per-partition sequentially with synchronous writes for failed or
> controlled shutdown brokers.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
