[jira] [Work started] (KAFKA-849) Bug in controller's startup/failover logic fails to update in memory leader and isr cache causing other state changes to work incorrectly

["Neha Narkhede (JIRA)" <ji...@apache.org>]

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

Work on KAFKA-849 started by Neha Narkhede.

> Bug in controller's startup/failover logic fails to update in memory leader and isr cache causing other state changes to work incorrectly
> -----------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: KAFKA-849
>                 URL: https://issues.apache.org/jira/browse/KAFKA-849
>             Project: Kafka
>          Issue Type: Bug
>          Components: controller
>    Affects Versions: 0.8
>            Reporter: Neha Narkhede
>            Assignee: Neha Narkhede
>            Priority: Blocker
>              Labels: kafka-0.8, p1
>
> partitionLeadershipInfo is the in memory cache of the controller that keeps track of every partition's "last elected" leader and isr. On controller startup/failover, this cache is bootstrapped only with those partitions whose leader is alive. This causes the leader and isr cache to be initialized incorrectly causing other state transitions related to new broker startup, existing broker failure to not work correctly. For instance, it does not allow the controller to send the list of *all* replicas that exist on a broker to it during startup.
> Another bug during controller startup is that it invokes OnlinePartition state change before OnlineReplica state change. This also breaks the guarantee that the controller sends a full list of replicas to a broker on startup

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