[
https://issues.apache.org/jira/browse/KAFKA-301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13259998#comment-13259998
]
Jun Rao commented on KAFKA-301:
-------------------------------
v3 looks good to me. A couple of minor comments:
31. ZkQueue: Is latestQueueItemPriority used to prevent sequential nodes being
added out of order in ZK? If so, should we log an error if this does happen?
32. StateChangeCommandHandler.run(): local vals topic, partition, and epoch are
not used.
> 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
> Assignee: Neha Narkhede
> Labels: replication
> Attachments: kafka-301-draft.patch, kafka-301-v1.patch,
> kafka-301-v2.patch, kafka-301-v3.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
