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
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
