Looping back on this for posterity. In case anyone else runs into this, the
solution was as follows:
- add a new node with the bogus broker ID
- let the cluster equilibrate / expand ISR sets
- move any partitions that have been assigned to this broker to the other
(original) brokers in the cluster
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 br
