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

specifying a non-existent broker to ./bin/kafka-reassign-partitions.sh leads to reassignment never getting completed.

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Open
    • Priority: Critical
    • Resolution: Unresolved
    • Affects Version/s: 0.10.1.1
    • Fix Version/s: None
    • Component/s: controller, tools
    • Labels:
    • Environment:
      Ubuntu-VERSION="14.04.5 LTS"

      Description

      Specifying a non-existent broker to ./bin/kafka-reassign-partitions.sh leads to reassignment never getting completed. 

       My reassignment is getting struck if I provide non-existing broker ID. My kafka version is 0.10.1.1.

       

       

      ./kafka-reassign-partitions.sh --zookeeper zk:2181 --reassignment-json-file le.json --execute
      Current partition replica assignment
      
      {"version":1,"partitions":[{"topic":"cv-topic","partition":0,"replicas":[1011131,101067,98,101240]}]}
      Save this to use as the --reassignment-json-file option during rollback
      Successfully started reassignment of partitions.
      

      In this 98 is the non-existing broker. Deleting reassign_partitions znode is of no use as well. As when I describe the same topic the 98 broker is out of sync.

       

       

      Topic:cv-topic PartitionCount:1 ReplicationFactor:4 Configs:
      Topic: cv-topic Partition: 0 Leader: 1011131 Replicas: 1011131,101067,98,101240 Isr: 1011131,101067,101240
      
      

      Now 98 will always be out of sync.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              raunak Ron1994
            • Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: