[
https://issues.apache.org/jira/browse/KAFKA-301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13249448#comment-13249448
]
Neha Narkhede commented on KAFKA-301:
-------------------------------------
The refactoring in KAFKA-307 attempted to reduce such interdependencies amongst
the various server components. Your suggestion of keeping all logic related to
managing replicas in ReplicaManager makes a lot of sense. However, it seems
like a good idea to keep all ZK specific logic bundled inside KafkaZookeeper.
Also, ideally, LogManager, ReplicaManager and KafkaZookeeper should really not
know about each other. Only KafkaServer "manages" these sub-components.
> 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
