You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Jason Gustafson (JIRA)" <ji...@apache.org> on 2015/09/02 20:36:46 UTC

[jira] [Commented] (KAFKA-2397) leave group request

    [ https://issues.apache.org/jira/browse/KAFKA-2397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14727809#comment-14727809 ] 

Jason Gustafson commented on KAFKA-2397:
----------------------------------------

Bumping this issue. One nice thing about the current patch is its simplicity (should be similar with the un-heartbeat approach). I wonder if it would be a bad thing to support explicit group departure with this patch and implicit departure with TCP disconnect? Then we could let this patch go through and consider the TCP disconnect in another JIRA.

> leave group request
> -------------------
>
>                 Key: KAFKA-2397
>                 URL: https://issues.apache.org/jira/browse/KAFKA-2397
>             Project: Kafka
>          Issue Type: Sub-task
>          Components: consumer
>            Reporter: Onur Karaman
>            Assignee: Onur Karaman
>            Priority: Minor
>             Fix For: 0.8.3
>
>
> Let's say every consumer in a group has session timeout s. Currently, if a consumer leaves the group, the worst case time to stabilize the group is 2s (s to detect the consumer failure + s for the rebalance window). If a consumer instead can declare they are leaving the group, the worst case time to stabilize the group would just be the s associated with the rebalance window.
> This is a low priority optimization!



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)