[
https://issues.apache.org/jira/browse/KAFKA-2397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14731073#comment-14731073
]
Jason Gustafson commented on KAFKA-2397:
----------------------------------------
[~jkreps] Not having a way to properly leave the group is pretty painful in
testing, which I imagine users are going to be doing a lot of initially. I
think it also makes rolling upgrades trickier if you don't have it since you
have to allow additional time for the group to stabilize after each machine is
upgraded. The ideal workflow to minimize rebalance overhead would probably be
to shutdown one instance, let the group stabilize, then restart it. If you just
restart the instance, then the whole group will have to pause until the old
member's session timeout has expired (Although you can also get around this by
persisting the consumer id).
Anyway, I'd rather have something if possible, but I agree that it could be
pushed to another release if we think the TCP option is the way forward.
> 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)
