kafka-jira mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jun Rao (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (KAFKA-5501) use async zookeeper apis everywhere
Date Wed, 26 Jul 2017 06:37:00 GMT

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

Jun Rao resolved KAFKA-5501.
----------------------------
       Resolution: Fixed
    Fix Version/s: 1.0.0

Issue resolved by pull request 3427
[https://github.com/apache/kafka/pull/3427]

> 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)

Mime
View raw message