When a broker starts up, it receives a LeaderAndIsrRequest from the controller broker telling the broker which partitions it should host and either lead or follow those partitions. If clients send requests to the broker before it has received this request, it throws this error you see. Did you restart the broker very quickly?
You can mitigate this issue by using controlled shutdown to stop a broker. Thanks, Neha On Oct 4, 2013 2:45 AM, "Aniket Bhatnagar" <aniket.bhatna...@gmail.com> wrote: > Because Kafka was detecting localhost.domain as hostname, I commented out > the line "127.0.0.1 localhost.localdomain localhost" and added > "127.0.0.1 ip-10-0-1-20.localdomain" in etc/hosts. When I restart Kafka > (issues kill -15 pid), writes to existing topics are failing and I see > several of the following errors: > > [2013-10-04 03:43:23,565] WARN [KafkaApi-1] Produce request with > correlation id 12868451 from client on partition > [consumertracking.gnomes.4002,5] failed due to Partition > [consumertracking.gnomes.4002,5] doesn't exist on 1 > (kafka.server.KafkaApis) > > > I have checked the kafka data directory and all files are intact. What > could have caused this issue and how can it be fixed? >
