[KAFKA-307] Refactor server code to remove interdependencies between LogManager and KafkaZooKeeper

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.7, 0.8.0
• Assignee: Neha Narkhede
• Reporter: Neha Narkhede
• Created: 16/Mar/12 01:14
• Updated: 23/Mar/12 20:20
• Resolved: 23/Mar/12 20:20

Description

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.

Issue Links

• blocks: KAFKA-45 Broker startup, leader election, becoming a leader/follower for intra-cluster replication