Uploaded image for project: 'Kafka'
  1. Kafka
  2. KAFKA-47 Create topic support and new ZK data structures for intra-cluster replication
  3. KAFKA-329

Remove the watches/broker for new topics and partitions and change create topic admin API to send start replica state change to all brokers

Attach filesAttach ScreenshotVotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 0.8.0
    • 0.8.0
    • None

    Description

      Currently in 0.8, all brokers register a watch on /brokers/topics and /brokers/topics/[topic] for all topics in a Kafka cluster. The watches are required to discover new topics.
      There is another way this can be achieved, as proposed here - https://cwiki.apache.org/confluence/display/KAFKA/Kafka+replication+detailed+design+V2#KafkareplicationdetaileddesignV2-Createtopic

      Basically, the create-topic admin command sends start-replica state change request to all brokers in the assigned replicas list.

      Attachments

        1. KAFKA-329-DRAFT.patch
          29 kB
          Prashanth Menon
        2. KAFKA-329-DRAFT-v2.patch
          33 kB
          Prashanth Menon
        3. KAFKA-329-v1.patch
          40 kB
          Prashanth Menon

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            prashanth.menon Prashanth Menon
            nehanarkhede Neha Narkhede
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment