kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jun Rao (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-362) ZookeeperConsumerConnector needs to connect to new leader after leadership change
Date Mon, 04 Jun 2012 15:51:23 GMT

    [ https://issues.apache.org/jira/browse/KAFKA-362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13288640#comment-13288640
] 

Jun Rao commented on KAFKA-362:
-------------------------------

In trunk, a partition only exists in 1 broker. So, once the partition assignment is done,
the set of brokers from which a consumer fetches data doesn't change. In 0.8, each partition
can have several replicas and data can only be fetched from the leader broker, which can change
over time. So, a consumer needs to handle leader change properly in 0.8.
                
> 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
>   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

        

Mime
View raw message