[jira] [Issue Comment Edited] (KAFKA-301) Implement the broker startup procedure

["Neha Narkhede (Issue Comment Edited) (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KAFKA-301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13249448#comment-13249448 ] 

Neha Narkhede edited comment on KAFKA-301 at 4/8/12 2:21 AM:
-------------------------------------------------------------

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. Ideally, LogManager, ReplicaManager and KafkaZookeeper should really not know about each other. Only KafkaServer "manages" these sub-components. But, in reality, it could be slightly difficult to keep these sub components completely independent of each other.
                
      was (Author: nehanarkhede):
    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, kafka-301-v1.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