You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Neha Narkhede (JIRA)" <ji...@apache.org> on 2013/05/29 02:20:19 UTC

[jira] [Updated] (KAFKA-923) Improve controller failover latency

     [ https://issues.apache.org/jira/browse/KAFKA-923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Neha Narkhede updated KAFKA-923:
--------------------------------

    Status: Patch Available  (was: Open)
    
> Improve controller failover latency
> -----------------------------------
>
>                 Key: KAFKA-923
>                 URL: https://issues.apache.org/jira/browse/KAFKA-923
>             Project: Kafka
>          Issue Type: Improvement
>          Components: controller
>    Affects Versions: 0.8
>            Reporter: Neha Narkhede
>            Assignee: Neha Narkhede
>            Priority: Critical
>              Labels: kafka-0.8
>
> During controller failover, we do the following things -
> 1. Increment controller epoch 
> 2. Initialize controller context
> 3. Initialize replica state machine
> 4. Initialize partition state machine
> During step 2 above, we read the information of all topics and partitions, the replica assignments and leadership information. During step 3 and 4, we re-read some of this information from zookeeper. Since the zookeeper reads are proportional to the number of topics and the reads are serial, it is important to optimize this. The zookeeper reads in steps 3 and 4 are not required.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira