-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consumers in a consumer group stuck for 4 days after ErrOffsetOutOfRange error #2855
Comments
@dnwe can you help with this issue? Again faced the same problem, consumers getting stuck for longer period of time. |
@shubham-dogra-s1 👋🏻 thanks for getting in touch The first thing to double check would be your consumer group lag vs the topic retention. If the group is too far behind in committed offset to keep up with the retention, then it is possible the log has been truncated and your client is trying to consume from an older offset that no longer exists |
@dnwe yes that is possible. I can see that in the lib code we are resetting the offset if we got ErrOffsetOutOfRange error Line 1123 in 4ad3504
Even though it is handled but still resulting in infinite loop somehow But we recently faced the same issue with another error On restarting the pods, consumers starting working again. |
Attaching some more logs regarding Logs from client
Kafka Exporter Logs
|
Thank you for taking the time to raise this issue. However, it has not had any activity on it in the past 90 days and will be closed in 30 days if no updates occur. |
Thank you for taking the time to raise this issue. However, it has not had any activity on it in the past 90 days and will be closed in 30 days if no updates occur. |
Hi @shubham-dogra-s1, I faced a similar issue(
|
Description
We recently noticed in our staging and prod environment that consumer groups got stuck for more than 4 days and not consuming messages from the partition. After restarting the pods it started working again.
Related Issue: #2682
Versions
Configuration
Logs
Additional Context
Faced the same behaviour with this error as well
Request exceeded the user-specified time limit in the request
The text was updated successfully, but these errors were encountered: