Hi, Kevin, Thanks for the KIP. A few comments.
JR1. I guess this is only intended for dynamic KRaft quorums? If so, it would be useful to clarify that. JR2. kafka-metadata-quorum remove-controller --controller-id 9990 --controller-directory-id EXAMPLE_UUID --unregister So, the existing remove-controller logic only changes the voter set, but doesn't unregister the controller? Should we just always do these two together? Is there a use case for only removing a controller from the voter set, but not unregsitering? JR3. Is kafka-cluster unregister-controller equivalent to kafka-metadata-quorum remove-controller --controller-id 9990 --controller-directory-id EXAMPLE_UUID --unregister? JR4. Could you describe the underlying workflow for each new command (RPCs sent, metadata records generated, actions taken by the controller, etc)? JR5. "The registration manager of an unregistered controller already attempts to re-register with the active controller. This is to prevent accidental unregistrations." I don't quite understand this. Why will an unregistered controller attempt to re-register? Jun On Fri, Apr 3, 2026 at 11:31 AM Kevin Wu <[email protected]> wrote: > Hi all, > > I would like to start a discussion on KIP-1312: Support unregistering > controllers. Below is the KIP link. > > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-1312%3A+Support+unregistering+controllers > > Thanks, > Kevin Wu >
