You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Guozhang Wang (JIRA)" <ji...@apache.org> on 2016/04/14 03:09:25 UTC
[jira] [Resolved] (KAFKA-3470) Consumer group coordinator should
take commit requests as effective as heartbeats
[ https://issues.apache.org/jira/browse/KAFKA-3470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Guozhang Wang resolved KAFKA-3470.
----------------------------------
Resolution: Fixed
Fix Version/s: 0.10.0.0
Issue resolved by pull request 1206
[https://github.com/apache/kafka/pull/1206]
> Consumer group coordinator should take commit requests as effective as heartbeats
> ---------------------------------------------------------------------------------
>
> Key: KAFKA-3470
> URL: https://issues.apache.org/jira/browse/KAFKA-3470
> Project: Kafka
> Issue Type: Improvement
> Reporter: Zaiming Shi
> Assignee: Jason Gustafson
> Fix For: 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
> delayed.
> 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.
> [For reference]
> previous discussions in: users@kafka.apache.org
> mail title: consumer group, why commit requests are not considered as effective heartbeats?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)