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

Neha Narkhede updated KAFKA-301:
--------------------------------

    Attachment: kafka-301-draft.patch

This patch adds the state change listeners, al though they will be exercised 
only when KAFKA-302 is in.

1. Introduced ZKQueue to communicate state change requests from the leader to 
the followers

2. State change requests are persistent, since some state changes need to be 
communicated even when the follower is not up (e.g delete topic)

3. Introduced leader epochs. The follower can skip certain state change 
requests if the request epoch is less than the current epoch for that partition

4. Added tests for the ZKQueue, and left TODOs for testing 
StateChangeRequestHandler. These tests can be added as part of KAFKA-302
                
> Implement the broker startup procedure
> --------------------------------------
>
>                 Key: KAFKA-301
>                 URL: https://issues.apache.org/jira/browse/KAFKA-301
>             Project: Kafka
>          Issue Type: Sub-task
>            Reporter: Neha Narkhede
>         Attachments: kafka-301-draft.patch
>
>
> This JIRA will involve implementing the list of actions to be taken on broker 
> startup, as listed by the brokerStartup() and startReplica() algorithm in the 
> Kafka replication design doc. Since the stateChangeListener is part of 
> KAFKA-44, this JIRA can leave it as a stub.

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

        

Reply via email to