-
Notifications
You must be signed in to change notification settings - Fork 226
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
Consumption paused indefinitely with out of order commit enabled #304
Comments
I'm experiencing the same issue. I also use out of order commits so the indefinite pause in consumption is probably from the same reason. It's a critical problem for us, and we're keenly looking for a resolution or workaround. |
I have asked a question at the subject related to the addition of |
@garyrussell @artembilan WDYT? I'd love to hear your thoughts on this |
Gary is not with our team any more, so don't expect any answers from him. |
@artembilan I'm not sure what's the bug exactly but if I'll find it I will contribute the fix. Do you you'll get the time to look at it at the following days? That's a pretty terrible bug because it requires a person to manually restart the pods when it happens so the consumption will resume. |
We use reactiveKafkaConsumerTemplate to receive messages, then Acknowledge the offset after processing the message. We enabled the out of order commit (maxDeferredCommits=250) and noticed the consumer paused indefinitely in certain situations.
stackoverflow
The events pattern are:
Logs:
code detail:
The text was updated successfully, but these errors were encountered: