samza-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jagadish Venkatraman <jagadish1...@gmail.com>
Subject Re: Producer stopped during leader switch
Date Tue, 01 Nov 2016 04:58:59 GMT
Hey David,

Apologies for the delayed response. There are a bunch of producer *send*
issues that were fixed in samza-11 (SAMZA-1028, SAMZA-1003). With Samza-11,
there's improved resiliency and if retries fail, the exception will be
propagated to your *StreamTask*, and will end up failing the container (if
you don't swallow it).

Thanks,
Jagadish



On Fri, Oct 28, 2016 at 10:12 AM, David Yu <david.yu@optimizely.com> wrote:

> Hi,
>
> We recently experienced a Kafka broker crash. When a new broker was brought
> up, we started seeing the following errors in Samza (0.10.1):
>
> WARN  o.a.k.c.producer.internals.Sender - Got error produce response with
> correlation id 5199601 on topic-partition
> session_key_partitioned_sessions-39, retrying (2147483646 attempts left).
> Error: NOT_LEADER_FOR_PARTITION
>
> Is the Producer not able to detect the new broker/leader for that
> partition?
>
> Thanks,
> David
>



-- 
Jagadish V,
Graduate Student,
Department of Computer Science,
Stanford University

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message