Libo,
Did you see this error in the broker 3's log, right after it was restarted?
One of the reasons for this error is that the broker hasn't received the
first LeaderAndIsr request from the controller yet. When a broker starts
up, the only way it knows what partitions it owns is through the first
This is from the broker 3's log:
[2013-08-22 15:40:02,984] WARN [KafkaApi-3] Fetch request: Partition [tes
t.replica1.default,0] doesn't exist on 3 (kafka.server.KafkaApis)
Here is what list topic command shows:
topic: test.replica1.defaultpartition: 0leader: 3 replicas: 3
isr:
