From 870a76bdc1d0889b498a84bf1ab00b35e8b8aaec Mon Sep 17 00:00:00 2001 From: asingh Date: Mon, 29 Jun 2015 17:45:36 -0700 Subject: [PATCH] KAFKA-972: MetadataRequest returns stale list of brokers --- core/src/main/scala/kafka/controller/KafkaController.scala | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/core/src/main/scala/kafka/controller/KafkaController.scala b/core/src/main/scala/kafka/controller/KafkaController.scala index 3635057..f37ab16 100755 --- a/core/src/main/scala/kafka/controller/KafkaController.scala +++ b/core/src/main/scala/kafka/controller/KafkaController.scala @@ -399,7 +399,7 @@ class KafkaController(val config : KafkaConfig, zkClient: ZkClient, val brokerSt // send update metadata request for all partitions to the newly restarted brokers. In cases of controlled shutdown // leaders will not be elected when a new broker comes up. So at least in the common controlled shutdown case, the // metadata will reach the new brokers faster - sendUpdateMetadataRequest(newBrokers) + sendUpdateMetadataRequest(controllerContext.liveBrokerIds.toSeq) // the very first thing to do when a new broker comes up is send it the entire list of partitions that it is // supposed to host. Based on that the broker starts the high watermark threads for the input list of partitions val allReplicasOnNewBrokers = controllerContext.replicasOnBrokers(newBrokersSet) -- 2.3.2 (Apple Git-55)