Affects Version/s: None
Fix Version/s: 0.10.0.0
Group coordinator does not reset heartbeat timer when commit request is received.
This may lead to unnecessary session timeouts when a consumer sends
sync commit requests so frequently that causes heartbeat requests to be
Presumably (as I do not know Kafka code well):
Commit requests (v1 and v2) have all data fields for a heartbeat request,
If they are taken as effective as heartbeat requests, we should have
better group stability.
previous discussions in: firstname.lastname@example.org
mail title: consumer group, why commit requests are not considered as effective heartbeats?