You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Jun Rao (Updated) (JIRA)" <ji...@apache.org> on 2012/02/09 03:15:59 UTC
[jira] [Updated] (KAFKA-265) Add a queue of zookeeper notifications
in the zookeeper consumer to reduce the number of rebalancing attempts
[ https://issues.apache.org/jira/browse/KAFKA-265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jun Rao updated KAFKA-265:
--------------------------
Attachment: kafka-265.patch
> Add a queue of zookeeper notifications in the zookeeper consumer to reduce the number of rebalancing attempts
> -------------------------------------------------------------------------------------------------------------
>
> Key: KAFKA-265
> URL: https://issues.apache.org/jira/browse/KAFKA-265
> Project: Kafka
> Issue Type: Sub-task
> Components: core
> Affects Versions: 0.7
> Reporter: Neha Narkhede
> Assignee: Jun Rao
> Fix For: 0.7.1
>
> Attachments: kafka-265.patch
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> The correct fix for KAFKA-262 and other known issues with the current consumer rebalancing approach, is to get rid of the cache in the zookeeper consumer.
> The side-effect of that fix, though, is the large number of zookeeper notifications that will trigger a full rebalance operation on the consumer.
> Ideally, the zookeeper notifications can be batched and only one rebalance operation can be triggered for several such ZK notifications.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira