Re: Producer stopped during leader switch
Just a follow up question - was a container failing with this error? And if it was - when it was restarted somewhere else, was it still getting the error? On Fri, Oct 28, 2016 at 10:12 AM, David Yuwrote: > 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 >
Re: Producer stopped during leader switch
That's good news. Thanks. On Mon, Oct 31, 2016 at 9:59 PM Jagadish Venkatramanwrote: > 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 > 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 > <(214)%20748-3646> 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 >
Re: Producer stopped during leader switch
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 Yuwrote: > 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
Producer stopped during leader switch
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