Hi Ashu, thanks for the tip. We have tried restarting the consumer, but that did not help. All read_committed consumers for this partition (we have multiple) have the same issue.
The partition already had different leaders, when we performed a rolling-restart of the brokers. All brokers give the same stuck LSO, so I don't think deleting will the partition will help? It will then restore the partition from another in-sync replica but that also has the incorrect LSO? Best, Pieter ________________________________ Van: Ashutosh singh <getas...@gmail.com> Verzonden: woensdag 20 november 2019 14:43 Aan: users@kafka.apache.org <users@kafka.apache.org> Onderwerp: Re: Last Stable Offset (LSO) stuck for specific topic partition after Broker issues Hello Pieter, We had similar issue. Did you try restarting your consumer ? It that doesn't fix then you can try deleting that particular topic partition from the broker and restart the broker so that it will get in sync. Please make sure that you have replica in-sync before deleting the partition. Thanks Ashu On Wed, Nov 20, 2019 at 6:57 PM Pieter Hameete <pieter.hame...@blockbax.com> wrote: > Hello, > > after having some Broker issues (too many open files) we managed to > recover our Brokers, but read_committed consumers are stuck for a specific > topic partition. It seems like the LSO is stuck at a specific offset. The > transactional producer for the topic partition is working without errors so > the latest offset is incrementing correctly and so is transactional > producing. > > What could be wrong here? And how can we get this specific LSO to be > increment again? > > Thank you in advance for any advice. > > Best, > > Pieter > -- Thanx & Regard Ashutosh Singh 08151945559
