[
https://issues.apache.org/jira/browse/KAFKA-2397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14659275#comment-14659275
]
Jason Gustafson commented on KAFKA-2397:
----------------------------------------
[~jkreps] I think the disconnect approach could be interesting if it was
tractable in the code, but I'm a little concerned that it would lead to
spurious rebalancing due to ephemeral network events. This might not be a big
deal when the consumers are in the same data center as the Kafka cluster, but
it could be a bigger problem if they have to cross the Internet. I wonder if
you could even get into some bad situations where network instability leads to
constant rebalancing as consumers leave and immediately join repeatedly.
> 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)
