[
https://issues.apache.org/jira/browse/KAFKA-301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13237755#comment-13237755
]
Prashanth Menon edited comment on KAFKA-301 at 3/25/12 1:20 AM:
----------------------------------------------------------------
Haha, no problem Neha. I'll let you wrap up KAFKA-301 and I can get started on
KAFKA-302. If all goes well, I can get a patch in by Wednesday and after
reviews and adjustments, we should be able to commit by Friday.
We should also probably go ahead and remove KAFKA-44?
was (Author: prashanth.menon):
Haha, no problem Neha. I'll let you wrap up KAFKA-301 and I can get
started on KAFKA-302. If all goes well, I can get a patch in by Wednesday and
after reviews and adjustments, we should be able to commit by Friday.
> 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
