[Question] Specified group generation id is not valid

The groupGenerationId is something we get from the broker (generation_id) in the JoinGroup response, and it’s just a number that increments with each generation in the group.

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.

The consumers that encounters that error become a kind of Zombie. They are still connected as consumers to a partition but not consuming messages.

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.

Hello guys

I am having this issue when I scale my application horizontally. The pod is processing normally and out of nowhere I get this error:

I suspect a rebalance has occurred and the pod still tries to commit a message. I’ve tried the above solutions but to no avail.