[ https://issues.apache.org/jira/browse/KAFKA-301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13237404#comment-13237404 ]
Neha Narkhede commented on KAFKA-301: ------------------------------------- Yeah, after finishing up on KAFKA-300, I took up this one and while working on it, the line between KAFKA-44 and this one started blurring. Though the real piece of work would be KAFKA-302. Sorry, didn't mean to step on someone else's toes. Just want to clear the path to let my work on KAFKA-46 progress. Having said that, do you want to pick up KAFKA-302 or even pick up this one ? I actually don't mind anything as long as we have KAFKA-45 resolved by next week. > 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 > 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