Few more questions actually AH1 Thanks, I was mainly trying to understand if dynamic reconfiguration offers an incomplete downscaling UX without this KIP. Seems like that's the case. I also missed the scenario with observer controllers so thanks for clarifying that part.
AH2 > The registration manager of an unregistered controller should attempt to > re-register with the active controller. This is to prevent accidental > unregistrations. I'm not sure if this makes sense to me, what would be an accidental unregistration? Is the only trigger for unregistration the new remove-controller command you're adding? AH3 > The intention for unregistration is for it to occur after the operator > decommissions a node which will no longer be part of the kafka cluster, and > is not expected to return. Why isn't the command expected to return? Thanks! On Fri, Apr 3, 2026 at 12:15 PM Alyssa Huang <[email protected]> wrote: > Thanks for the KIP Kevin! > > AH1 > >> This means a stale controller registration from a controller that no >> longer exists can block feature upgrades. > > > And dynamic reconfiguration (specifically RemoveVoter) can cause stale > controller registrations? Meaning anyone who has used RemoveVoter to > permanently downsize their controller quorum would eventually need to > unregister the controller to unblock future feature upgrades? > > Best, > Alyssa > > On Fri, Apr 3, 2026 at 11:30 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 >> >
