Hmm, then it's weird. Could you try the latest code in 0.8? If the problem persists, could you file a jira and attach the broker log?
Thanks, Jun On Wed, Apr 24, 2013 at 11:00 PM, Yin Yin <yin....@outlook.com> wrote: > With the option --unavailable-partitions --topic topic1, kafka-list-topic > doesn't show anything related to topic1> Date: Wed, 24 Apr 2013 20:58:09 > -0700 > > Subject: Re: LeaderNotAvailable Exception > > From: jun...@gmail.com > > To: users@kafka.apache.org > > > > What output do you get if you add the --unavailable-partitions option in > > list topic? > > > > Thanks, > > > > Jun > > > > > > On Wed, Apr 24, 2013 at 5:20 PM, Yin Yin <yin....@outlook.com> wrote: > > > > > This exception happens only once. But there is another error for each > > > producer request > > > [2013-04-24 14:47:39,077] WARN [KafkaApi-0] Produce request: Leader > not > > > local for partition [topic1,0] on broker 0 (kafka.server.KafkaApis) > Here > > > is the information I get from kafka-list-topic, which indicates that > > > borker0 is the leader for topic1 and partition 0 [2013-04-24 > 14:56:03,948] > > > INFO zookeeper state changed (SyncConnected) > (org.I0Itec.zkclient.ZkClient) > > > topic: topic1 partition: 0 leader: 0 replicas: 0 isr: 0 > > > > > From: libo...@citi.com > > > > To: users@kafka.apache.org > > > > Subject: Re: LeaderNotAvailable Exception > > > > Date: Wed, 24 Apr 2013 17:38:23 +0000 > > > > > > > > Hi Jun, > > > > > > > > This exception also gave me a hard time. In my case, I didn't create > the > > > topic > > > > before using it for producing. > > > > > > > > Regards, > > > > > > > > Libo > > > > > > > > > > > >
