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 < [email protected]> 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 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=none, startup fails with: > org.apache.kafka.streams.errors.StreamsException: No valid committed > offset found for input [myTopic] and no valid reset policy configured > Important notes: > > * application.id is explicitly configured and static. > * The same topology and configuration on the older stack works fine > and retains offsets across restart. > I have only a basic familiarity with the Kafka Streams internals, but > while debugging StreamTask in 4.1.2, I see commit paths being reached even > though no actual offsets seem to be committed. > > Has anyone seen this in 4.1.x, or does this match any known issue? > Any pointers, similar bug reports, or things I should inspect next would > be greatly appreciated. > Thanks > > > >
