Unfortunately, we don't have access to producer log. But it seems very obvious 
to me that producer
failed to find out the correct leader as the warning messages occurred 
repetitively for a 
pretty long time span (more than 10 minutes).

Regards,

Libo


-----Original Message-----
From: Guozhang Wang [mailto:wangg...@gmail.com] 
Sent: Thursday, November 14, 2013 11:48 AM
To: users@kafka.apache.org
Subject: Re: Leader not local

Hi Libo,

Yes the producer should be start to find the correct leader upon just one send 
failures. Could you check if there are other exceptions on the producer log?

Guozhang


On Thu, Nov 14, 2013 at 8:23 AM, Yu, Libo <libo...@citi.com> wrote:

> Hi team,
>
> I saw this line within a long time span in our logs for the same topic 
> and partition.
> [2013-11-14 11:13:41,647] WARN [KafkaApi-1] Produce request with 
> correlation id 529240 from client  on partition [mytopic,2] failed due 
> to Leader not local for partition [mytopic,2] on broker 1
> (kafka.server.KafkaApis)
>
> Why can't the producer find out the broker it is publishing to is not 
> the broker in this case? I believe it should find it out and publish 
> to the leader broker.
>
>
> Regards,
>
> Libo
>
>


--
-- Guozhang

Reply via email to