-
-
Notifications
You must be signed in to change notification settings - Fork 523
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
[Question] Specified group generation id is not valid #1009
Comments
That's a server error, how are you generating your group ids? |
the groupId looks like: ${Environment}-staticString
|
The You'll get this error when you try to commit after having been kicked out of the consumer group. This could for example happen if you spend too long in between heartbeats (because you're processing a single message for too long, for example). What should happen is that you should re-join the group and get the new generation id to use. It would be helpful if you could run with DEBUG log level so that we can see what requests are being made when this happens.
This is a shot in the dark, but do you maybe have more consumer instances than you do partitions? If so, some of your consumers will not be assigned any partitions, and thus won't be doing any work. |
I'll enable debug log level and will post once the error occurs. Regarding more consumers than partitions - we are running on ECS with autoscaling, max tasks=60 (each task = 1 consumer). The topic configured with 60 partitions. I'm pretty sure that we didn't reached to the max number of tasks, but i'll check it also once the error occurs. |
Hello, I'm having a similar issue. Could increasing the heartbeatInterval and sessionTimeout potentially fix the issue? I think I'm taking too long while processing when making a network request with high latency. |
Yes. You have to tweak those to fit your application behavior. |
Thanks. It fixed my issue. |
This error is indicating that the consumer is trying to commit offsets, but the consumer group has changed to a new generation. Retrying within the existing session will indeed not work, but rejoining the group and re-trying should be successful. Fixes tulios#1009
This error is indicating that the consumer is trying to commit offsets, but the consumer group has changed to a new generation. Retrying within the existing session will indeed not work, but rejoining the group and re-trying should be successful. Fixes tulios#1009
This error is indicating that the consumer is trying to commit offsets, but the consumer group has changed to a new generation. Retrying within the existing session will indeed not work, but rejoining the group and re-trying should be successful. Fixes tulios#1009
Describe the bug
Consumers (sometimes) encounters the following exception:
Specified group generation id is not valid
. The consumers that encounters that error become a kind of Zombie. They are still connected as consumers to a partition but not consuming messages.To Reproduce
Can't reproduce
Expected behavior
The consumer should reconnect to the consumer grouop.
Observed behavior
Logs:
Environment:
Additional context
It's probably not related to KafkaJs, but there is a mention of that error error.js and maybe you have any idea why it's happening?
The text was updated successfully, but these errors were encountered: