Hi, Which version of Kafka are you running? We run thousands of clusters, and typically use this mechanism for replacing damaged hardware, and we've only seen this issue under Kafka 0.8, where the controller can get stuck (due to a few bugs in Kafka) and not be functioning. If you are on 0.8, I'd recommend moving off it as soon as possible. In the meantime, check out the JMX bean for kafka.controller:type=KafkaController,name=ActiveControllerCount on all your active brokers - if it's zero, then that's an indication of this bug.
Thanks Tom On Tue, May 31, 2016 at 10:11 AM, Fredo Lee <buaatianwa...@gmail.com> wrote: > i find the new broker with old broker id always fetch message from itself > for the reason that it believe it's the leader of some partitions. > > 2016-05-31 15:56 GMT+08:00 Fredo Lee <buaatianwa...@gmail.com>: > > > we have a kafka cluster and one of them is down for the reason of disk > > damaged. so we use the same broker id in a new server machine. > > > > when start kafka in the new machine, lots of error msg: "[2016-05-31 > > 10:30:49,792] ERROR [ReplicaFetcherThread-0-1013], Error for partition > > [consup-0000000025,20] to broker 1013:class > > kafka.common.NotLeaderForPartitionException > > (kafka.server.ReplicaFetcherThread) > > " > > >
