[
https://issues.apache.org/jira/browse/KAFKA-2397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14659158#comment-14659158
]
Guozhang Wang commented on KAFKA-2397:
--------------------------------------
I once considered letting KafkaApis to handle connection closure when I was
working on purgatory re-design, to purge the requests as mentioned by Jar. The
difficulties are that at the socket server the connection is not logically tied
to a client (although in fact it is), while for handling a requests / client
failure events we need to pass-in a client-id into the API layer. A lot has
changed in SocketServer since then so I do not know if things have changed so
that we can infer the client-id (or more specifically consumer-id in this case)
from SocketServer.
> 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)
