You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Neha Narkhede (Updated) (JIRA)" <ji...@apache.org> on 2012/03/22 00:20:22 UTC
[jira] [Updated] (KAFKA-307) Refactor server code to remove
interdependencies between LogManager and KafkaZooKeeper
[ https://issues.apache.org/jira/browse/KAFKA-307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Neha Narkhede updated KAFKA-307:
--------------------------------
Attachment: (was: kafka-307-draft.patch)
> Refactor server code to remove interdependencies between LogManager and KafkaZooKeeper
> --------------------------------------------------------------------------------------
>
> Key: KAFKA-307
> URL: https://issues.apache.org/jira/browse/KAFKA-307
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 0.7, 0.8
> Reporter: Neha Narkhede
> Attachments: kafka-307-draft.patch
>
>
> Currently, LogManager wraps KafkaZooKeeper which is meant for all zookeeper interaction of a Kafka server. With replication, KafkaZookeeper will handle leader election, various state change listeners and then start replicas. Due to interdependency between LogManager and KafkaZookeeper, starting replicas is not possible until LogManager starts up completely. Due to this, we have to separate the broker startup procedures required for replication to get around this problem.
> It will be good to refactor and clean up the server code, before diving deeper into replication.
--
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