-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
unknown generation error while consuming using consumer group #1310
Comments
@bai have you seen this error ever? |
Possibly related? bsm/sarama-cluster#29 |
Thanks Bai, that's helpful. |
Hey @dim I think I need your help here. I have tried bunch things but still getting below error in sarama logs.
Here is my consumer side config -
redacted logs from kafka side -
|
@varun06 sorry, I have been slightly distracted recently :) My apologies, but I am not 100% sure how to help. Generation errors only happen when a member tries to commit offsets after the session has been closed server side. I assume you are not stopping your consume loop quickly enough after a rebalance is triggered. The broker is then starting a new session with a new generation and giving up on the previous one. I would try to increase the Session.Timeout and see if that makes a difference. |
Thanks @dim I have been playing with timeouts and they have helped, so errors are very sporadic now, I am sure it is the way we committing the offsets, we commit them in batch and that code has some oddities as you mentioned. |
@varun06 can you please describe and share your timeout values with us? We have the same problem with Sarama. |
|
Versions
Sarama Version:1.21.0
Kafka Version: 1.1.0
Go Version:1.12
Configuration
Logs
Problem Description
We have a library that provide some abstraction over sarama consumer group. while using the library I see lots of above ^^ errors. I have already looked at session timeout values, but no help. @dim can you please help me understand this error and point towards some steps?
The text was updated successfully, but these errors were encountered: