kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Neha Narkhede (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-343) revisit the become leader and become follower state change operations using V3 design
Date Mon, 06 Aug 2012 18:20:02 GMT

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

Neha Narkhede commented on KAFKA-343:
-------------------------------------

Yang,

Do we know the impact of this patch on the leader election latency ? The idea of having a
controller do state changes was the possible reduction in leader election latency. Curious
to know if there are any numbers to support this assumption ?


                
> revisit the become leader and become follower state change operations using V3 design
> -------------------------------------------------------------------------------------
>
>                 Key: KAFKA-343
>                 URL: https://issues.apache.org/jira/browse/KAFKA-343
>             Project: Kafka
>          Issue Type: Sub-task
>          Components: core
>    Affects Versions: 0.8
>            Reporter: Jun Rao
>            Assignee: Yang Ye
>             Fix For: 0.8
>
>         Attachments: kafka_343.diff.2, kafka_343.diff.3, kafka_343.diff.4, kafka_343.diff.5,
kafka_343.diff.6, kafka_343.patch, kafka_343_v7.patch, kafka_343_v8.patch
>
>
> We need to reimplement become leader/follower using the controller model described in
https://cwiki.apache.org/confluence/display/KAFKA/kafka+Detailed+Replication+Design+V3

--
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