Hi Waseem, We had faced a similar issue before.. Have you monitored your application logs as to much time does it take your application to process one record(kafka event). In our case, this was the bottleneck. The consumer used to take too much time, so the consumer heatbeats stopped and next messages were not received. Do try and monitor your processing loop. By default kafka consumer has sane default configuration, so you need not tweak it but you can try and adapt it as per your use case.
Regards, Prasad Sawool On Thu, 7 Aug 2025 at 05:06, Waseem Anwar <was...@evolverstech.com> wrote: > Dear Apache Kafka Users, > > I hope you're doing well. > > I'm encountering an issue with our Kafka setup where the consumer stops > receiving messages after running for a period of time, even though: > > - > > The Kafka producer continues to send payloads successfully > - > > The consumer remains connected and shows no visible errors > - > > Restarting the consumer causes it to start receiving messages again > temporarily > - > > The messages are confirmed to be in the Kafka topic (e.g., via > kafka-console-consumer) > - > > There are no signs of consumer crashes or disconnections in the logs > > Our Kafka version is ruby-kafka (1.5.0) as we have integrated it into the > Ruby on Rails application. This behavior appears intermittent, and we’re > unsure whether it's related to offset management, consumer group behavior, > or something else. > > We would greatly appreciate your help in identifying what could be causing > this issue, or any suggestions on additional debugging steps we can take. > > Please let me know if further configuration or log details would be > helpful. > > Best regards, > > Waseem Anwar > Senior Software Engineer >
