[
https://issues.apache.org/jira/browse/KAFKA-2397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Onur Karaman updated KAFKA-2397:
--------------------------------
Description:
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!
was: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.
> 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)
