[jira] [Updated] (KAFKA-14909) KRaft Controllers not setting ZkMigrationReady tagged field

["David Arthur (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/KAFKA-14909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Arthur updated KAFKA-14909:
---------------------------------
        Parent: KAFKA-14304
    Issue Type: Sub-task  (was: Bug)

> KRaft Controllers not setting ZkMigrationReady tagged field
> -----------------------------------------------------------
>
>                 Key: KAFKA-14909
>                 URL: https://issues.apache.org/jira/browse/KAFKA-14909
>             Project: Kafka
>          Issue Type: Sub-task
>          Components: kraft
>    Affects Versions: 3.4.0
>            Reporter: David Arthur
>            Priority: Major
>             Fix For: 3.5.0, 3.4.1
>
>
> When sending ApiVersionsResponse to other controllers, the KRaft controller is not setting the ZkMigrationReady field. This means, we can't determine if the full KRaft quorum has been properly configured for a migration before triggering the migration.
> As a result, we could start the migration on controller A (which was properly configured), then fail over to controller B (which was not properly configured) and no longer be in dual-write mode.
> The fix is to properly set the ZkMigrationReady tagged field, and to make use of it in KRaftMigrationDriver



--
This message was sent by Atlassian Jira
(v8.20.10#820010)