Skip to main content

Posts

Re: Kafka Streams 4.1.2 offsets not being committed after upgrade from Spring Boot 3.5.8 to 4.0.5

Hi Lucas, This was indeed the issue, and your fix resolved it. Thanks for the assistance — greatly appreciated. Best, Yves. C2 - Restricted use ________________________________ Van: Lucas Brutschy via users <users@kafka.apache.org> Verzonden: maandag 27 april 2026 13:46 Aan: users@kafka.apache.org <users@kafka.apache.org> CC: Lucas Brutschy <lbrutschy@confluent.io> Onderwerp: Re: Kafka Streams 4.1.2 offsets not being committed after upgrade from Spring Boot 3.5.8 to 4.0.5 Hi Yves, do you use a consumer interceptor or wrapper that constructs ConsumerRecord objects using a deprecated pre-4.0 constructor? We have seen these problems when people use these kinds of outdated overloads; see https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcwiki.apache.org%2Fconfluence%2Fdisplay%2FKAFKA%2FKIP-1094%253A%2BAdd%2Ba%2Bnew%2Bconstructor%2Bmethod%2Bwith%2BnextOffsets%2Bto%2BConsumerRecords&data=05%7C02%7Cyves.stroucken%40soprasteria.co...

Re: Kafka Streams 4.1.2 offsets not being committed after upgrade from Spring Boot 3.5.8 to 4.0.5

Hi Yves, do you use a consumer interceptor or wrapper that constructs ConsumerRecord objects using a deprecated pre-4.0 constructor? We have seen these problems when people use these kinds of outdated overloads; see https://cwiki.apache.org/confluence/display/KAFKA/KIP-1094%3A+Add+a+new+constructor+method+with+nextOffsets+to+ConsumerRecords. If that is the case, the solution is to use the new overload. Cheers, Lucas On Fri, Apr 24, 2026 at 5:58 PM STROUCKEN Yves <yves.stroucken@soprasteria.com> wrote: > > Hi Bill, > > Thanks for the quick reply. > Here is some of the output I get with debug logging and kafka-consumer-groups.sh > > ./kafka-consumer-groups.sh \ > --bootstrap-server localhost:9092 \ > --describe \ > --group 'MyProcessingApplication' > > loging.level.org.apache.kafka.streams.processor.internals.StreamTask: DEBUG > > Starting with a clean topic with no events. > > output: ...

Re: Kafka Streams 4.1.2 offsets not being committed after upgrade from Spring Boot 3.5.8 to 4.0.5

Hi Bill, Thanks for the quick reply. Here is some of the output I get with debug logging and kafka-consumer-groups.sh ./kafka-consumer-groups.sh \ --bootstrap-server localhost:9092 \ --describe \ --group 'MyProcessingApplication' loging.level.org.apache.kafka.streams.processor.internals.StreamTask: DEBUG Starting with a clean topic with no events. output: GROUP TOPIC PARTITION CURRENT-OFFSET LOG-END-OFFSET LAG CONSUMER-ID HOST CLIENT-ID MyProcessingApplication myTopic.0 4 - 0 - MyProcessingApplication-509fdb18-f2ec-43f9-a214-50c3d309fde5-StreamThread-1-consumer-6a48934d-d93f-41d5-a89b-4faecaaba720 / hostIp MyProcessingApplication-509fdb18-f2ec-43f9-a214-50c3d309fde5-StreamThread-1-consumer MyProcessingApplication myTo...

Re: Kafka Streams 4.1.2 offsets not being committed after upgrade from Spring Boot 3.5.8 to 4.0.5

Sorry to hear about the issues. Can you provide log files to help diagnose the problem? Thanks, Bill On Fri, Apr 24, 2026 at 4:53 AM STROUCKEN Yves < yves.stroucken@soprasteria.com> wrote: > Hello Kafka users, > I am looking for help with a Kafka Streams offset commit issue that > started after upgrading. > We have a Spring Cloud Stream application using the Kafka Streams binder. > Old working stack: > > * Spring Boot 3.5.9 > * Spring Cloud 2025.0.0 > * spring-cloud-stream-binder-kafka-streams 4.3.0 > * kafka-streams 3.9.1 > New stack with the issue: > > * Spring Boot 4.0.5 > * Spring Cloud 2025.1.1 > * spring-cloud-stream-binder-kafka-streams 5.0.1 > * kafka-streams 4.1.2 > Broker version: > > * Kafka brokers 3.9.0 > Symptoms: > > * The Kafka Streams application processes new records normally. > * However, committed offsets for the S...

Kafka Streams 4.1.2 offsets not being committed after upgrade from Spring Boot 3.5.8 to 4.0.5

Hello Kafka users, I am looking for help with a Kafka Streams offset commit issue that started after upgrading. We have a Spring Cloud Stream application using the Kafka Streams binder. Old working stack: * Spring Boot 3.5.9 * Spring Cloud 2025.0.0 * spring-cloud-stream-binder-kafka-streams 4.3.0 * kafka-streams 3.9.1 New stack with the issue: * Spring Boot 4.0.5 * Spring Cloud 2025.1.1 * spring-cloud-stream-binder-kafka-streams 5.0.1 * kafka-streams 4.1.2 Broker version: * Kafka brokers 3.9.0 Symptoms: * The Kafka Streams application processes new records normally. * However, committed offsets for the Streams application do not appear to advance. * In Kafka UI, consumer group lag stays high for all partitions, while application-level metrics show near real-time processing of new events. * On restart, the application starts reading from the beginning of the topic again. * When I set auto.offset.reset=no...

Tiered Storage recovery after cluster Deletion

Hi Everyone, I wanted to understand if there is a way to recover topic data from Kafka tiered storage after the kafka cluster is deleted . The local data is gone but the data in tiered storage still exists. Is there a way to bring up a new kafka cluster and assign the same tiered storage bucket to it so its able to read data from it by resyncing the metadata? Thanks, Vruttant Mankad

Best practice for Kraft controller recovery during disaster

Hi Kafka experts, I am running kafka in windows platform. I have controllers (around 5) and brokers running in separate machines During disaster recovery (Say all controller machines data wiped out, or the controller logs folder is corrupt), but broker machines are intact. what is the best practice to bring the kraft controller back with metadata info? Regards, Nanda