[
https://issues.apache.org/jira/browse/KAFKA-2397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14652198#comment-14652198
]
Jason Gustafson commented on KAFKA-2397:
----------------------------------------
[~onurkaraman] I like this idea. Wouldn't the expected rebalance time actually
be just the heartbeat interval since that's how long it would take the other
group members to see the need to rebalance and send the new join group request?
I think [~jkreps] was also suggesting to implement this as an "un-heartbeat"
(i.e. with a flag on the heartbeat request), but I'm not sure if there was a
strong reason to prefer that over the explicit request.
> 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)
