[
https://issues.apache.org/jira/browse/KAFKA-2397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14696334#comment-14696334
]
Jiangjie Qin commented on KAFKA-2397:
-------------------------------------
[~ewencp] Are you saying that the coordinator should kick the consumer out of
group once its TCP connection is closed? I think the problem here is this
breaks the layers we have on broker side. So the TCP connections are only
maintained by SocketServer and not exposed to KafkaApiThreads. So SocketServer
does not know about which consumer a particular connection is associated with.
If you want to let Coordinator knows about TCP connection closure, the
coordinator needs to keep a consumer-socket map and SocketServer needs to
produce some event back to the request queue to notify a disconnection and
coordinator needs to check if that socket is associated with some consumer or
not.
> 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)
