We recently tried to rebalance partitions for a topic (via kafka.admin.ReassignPartitionsCommand).
In the .json file with the desired end-state, an id for a non-existent broker was entered for a partition. Upon --execute, all partitions were moved without issue, but the partition with the bogus broker ID was left stuck with an expanded replica set, and the repartition has failed to finish. This is presumably because the cluster is waiting indefinitely for this new broker to become available so the partition can be replicated there. Any thoughts on how to remove this bogus broker ID for this partition? Has anyone come up against this before? This is blocking us from being able to run additional repartitioning tasks on this cluster. Also - it seems like a repartitioning job should fail to execute if a broker id that does not exist is specified. That would have prevented this particular issue. Thanks in advance! - nick
