Hi, Pushkar.
As the error message shows, the error means that some messages couldn't be
produced successfully for 120 seconds.
There are many causes which could lead to this phenomenon, so it's hard to
tell the solution unless more information is provided.
For example:
- Kafka broker-side's issue:
* Too many replicas were down so couldn't produce
* Took too long time for leader-election after previous leader failed
- Producer-side's issue:
* Many TCP retransmissions due to unstable network
* Producer's I/O thread couldn't proceed due to busy CPU or long GC
pauses or something
etc.
These are just examples so still there are many other possibilities.
Did you get other errors on your producer? Also, were brokers fine around
the incidental time?
2022年4月5日(火) 15:22 Pushkar Deole <pdeole2...@gmail.com>:
> Liam,
>
> This is set to default and we have not changed these configurations. So
> from kafka docs, the default value of linger.ms for producer is 0
>
> On Tue, Apr 5, 2022 at 4:42 AM Liam Clarke-Hutchinson <lclar...@redhat.com
> >
> wrote:
>
> > Hi Pushkar,
> >
> > Could be a lot of things. What's your linger.ms configured for?
> >
> > Cheers,
> >
> > Liam
> >
> > On Tue, 5 Apr 2022 at 05:39, Pushkar Deole <pdeole2...@gmail.com> wrote:
> >
> > > Hi All,
> > >
> > > We are intermittently seeing KafkaProducerException. The nested
> exception
> > > is as below:
> > >
> > > org.springframework.kafka.core.KafkaProducerException: Failed to send;
> > > nested exception is org.apache.kafka.common.errors.TimeoutException:
> > > Expiring 10 record(s) for analytics.mpe.passthrough-0:120000 ms has
> > passed
> > > since batch creation\n\tat
> > > org.springframework.kafka.core.KafkaTemplate.lambda$buildCallback$4(
> > > KafkaTemplate.java:602 <http://kafkatemplate.java:602/>)
> > >
> > > Kafka version is 2.5
> > > Can someone give some ideas as to what would cause this and how can
> this
> > be
> > > resolved?
> > >
> >
>
--
========================
Okada Haruki
ocadar...@gmail.com
========================
