[
https://issues.apache.org/jira/browse/KAFKA-2397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14957718#comment-14957718
]
Guozhang Wang commented on KAFKA-2397:
--------------------------------------
For consumer shutdown, in the ZK-based consumer we will immediately delete its
ephemeral node so that other members will be notified, hence now in the new
consumer without this fix we are effectively introducing an regression.
For consumer hard failure cases though, with ZK-based old consumer it also
takes a session timeout period to be detected; so I feel modifying the socket
server to penetrate client-id information to pass to coordinator in order to
improve on this case may be an overkill.
> 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.9.0.0
>
>
> 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)
