[
https://issues.apache.org/jira/browse/KAFKA-1020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-1020:
---------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
Fixed as part of kafka-1202.
> Remove getAllReplicasOnBroker from KafkaController
> --------------------------------------------------
>
> Key: KAFKA-1020
> URL: https://issues.apache.org/jira/browse/KAFKA-1020
> Project: Kafka
> Issue Type: Bug
> Reporter: Guozhang Wang
> Assignee: Guozhang Wang
> Fix For: 0.8.1
>
> Attachments: KAFKA-1020.v1.patch
>
>
> Today KafkaController call getAllReplicasOnBroker on broker failure and new
> broker start up to get all the replicas that broker is holding (or suppose to
> hold). This function actually issue a read on each topic's partition znodes.
> With large number of topic/partitions this could seriously increase the
> latency of handling broker failure and new broker startup.
> On the other hand, ControllerContext maintains a partitionReplicaAssignment
> cache, which is designed to keep the most updated partition replica
> assignment according to ZK. So instead of reading from ZK, we could just read
> from the local cache, given that partitionReplicaAssignment is guaranteed to
> be up-to-date.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
