[
https://issues.apache.org/jira/browse/KAFKA-362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-362:
--------------------------
Attachment: kafka-362_v2.patch
Attache patch v2 with minor changes to make sure that no more fetcher threads
are started after stopAllConnections() is called in ConsumerFetcherManager.
> ZookeeperConsumerConnector needs to connect to new leader after leadership
> change
> ---------------------------------------------------------------------------------
>
> Key: KAFKA-362
> URL: https://issues.apache.org/jira/browse/KAFKA-362
> Project: Kafka
> Issue Type: Sub-task
> Components: core
> Affects Versions: 0.8
> Reporter: Jun Rao
> Assignee: Jun Rao
> Fix For: 0.8
>
> Attachments: kafka-362_v1.patch, kafka-362_v2.patch
>
> Original Estimate: 252h
> Remaining Estimate: 252h
>
> Currently, if the leader of a partition changes, the fetcher in
> ZookeeperConsumerConnector won't switch to the new leader automatically.
--
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
