Uploaded image for project: 'Kafka'
  1. Kafka
  2. KAFKA-307

Refactor server code to remove interdependencies between LogManager and KafkaZooKeeper

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 0.7, 0.8.0
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      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.

        Attachments

        1. kafka-307-draft.patch
          21 kB
          Neha Narkhede
        2. kafka-307-v2.patch
          22 kB
          Neha Narkhede
        3. kafka-307-v3.patch
          22 kB
          Neha Narkhede

          Issue Links

            Activity

              People

              • Assignee:
                nehanarkhede Neha Narkhede
                Reporter:
                nehanarkhede Neha Narkhede
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: