kevin-wu24 commented on PR #22191: URL: https://github.com/apache/kafka/pull/22191#issuecomment-5119507574
Hi @ChetanKoneru, Thanks for the questions. Please see the compatibility section and rejected alternatives sections of KIP-1312: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=406623954#KIP1312:Supportunregisteringcontrollers-Compatibility,Deprecation,andMigrationPlan. This feature only applies to new clusters going forward. In many cases, operators can "refresh" a stale controller registration by bringing up a controller with the same node id as the stale registration. I'm not familiar with Strimzi's operator, so I cannot speak to your specific case unfortunately. > Could you clarify whether this operation requires the cluster to have already finalized the metadata version that supports UnregisterControllerRecord (currently proposed as IBP_4_4_IV1)? Yes, clusters need a metadata version that supports the record to serialize and deserialize it. New metadata records must be gated behind new metadata versions. This is because a given metadata version must be supported by all nodes registered with the cluster to be finalized. > Is an in-place repair path for clusters stuck at an older finalized metadata version in scope for this PR or planned separately? This is not in scope for this PR or planned separately. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
