[
https://issues.apache.org/jira/browse/KAFKA-2397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14696351#comment-14696351
]
Jason Gustafson commented on KAFKA-2397:
----------------------------------------
[~ewencp] The only case I can come up with is an application timeout on the
client (e.g. if the heartbeat was delayed by a transient network issue), and
that can be fixed by always ensuring that the timeout for coordinator requests
is longer than the session timeout. My unease mostly has to do with
proxy/tunnel situations where I don't know that TCP always behaves properly.
Perhaps you know enough to know whether this is an issue? In any case, it seems
like we all agree that we need a way to leave the group properly. My preference
is probably for Onur's patch as it stands now.
> 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)
