[
https://issues.apache.org/jira/browse/KAFKA-2397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14659470#comment-14659470
]
Jay Kreps commented on KAFKA-2397:
----------------------------------
[~guozhang] I haven't thought this through but here is the basic idea. For the
purgatory case I think when you added something to the purgatory you would also
add a "shutdown action" to the session that would delete the item on session
termination. The session concept is what ties the KafkaApi layer to the network
layer so this could be added in handleProduce().
[~hachikuji] Makes sense. Theoretically TCP should handle it, but yeah anything
which broke the tcp connections would issue a rebalance storm.
> 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)
