Re: Facing Duplication in consumer
If the consumer is idle (not doing any commit) for more than a day, the offsets will be wiped out. Rf. offsets.retention.minutes property in Kafka documentation. On Tue, May 29, 2018 at 9:49 AM, Shantanu Deshmukh wrote: > Which Kafka version? > > On Mon, May 28, 2018 at 9:09 PM Dinesh Subramanian < > dsubraman...@apptivo.co.in> wrote: > > > Hi, > > > > Whenever we bounce the consumer in tomcat node, I am facing duplication. > > It is consumed from the beginning. I have this property in consumer > > "auto.offset.reset" = "earliest". if it is new consumer means it will > > consume from the beginning, but it is consumed from the beginning for the > > consumer that we used for last 4 months and consumer offset is committed > > already in partition wise. Any help will be appreciated. > > > > > > *Thanks & Regards,* > > > > *Dinesh S* > > >
Re: Facing Duplication in consumer
Which Kafka version? On Mon, May 28, 2018 at 9:09 PM Dinesh Subramanian < dsubraman...@apptivo.co.in> wrote: > Hi, > > Whenever we bounce the consumer in tomcat node, I am facing duplication. > It is consumed from the beginning. I have this property in consumer > "auto.offset.reset" = "earliest". if it is new consumer means it will > consume from the beginning, but it is consumed from the beginning for the > consumer that we used for last 4 months and consumer offset is committed > already in partition wise. Any help will be appreciated. > > > *Thanks & Regards,* > > *Dinesh S* >
Facing Duplication in consumer
Hi, Whenever we bounce the consumer in tomcat node, I am facing duplication. It is consumed from the beginning. I have this property in consumer "auto.offset.reset" = "earliest". if it is new consumer means it will consume from the beginning, but it is consumed from the beginning for the consumer that we used for last 4 months and consumer offset is committed already in partition wise. Any help will be appreciated. *Thanks & Regards,* *Dinesh S*