You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "David Arthur (Jira)" <ji...@apache.org> on 2023/04/14 19:31:00 UTC

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

David Arthur created KAFKA-14909:
------------------------------------

             Summary: KRaft Controllers not setting ZkMigrationReady tagged field
                 Key: KAFKA-14909
                 URL: https://issues.apache.org/jira/browse/KAFKA-14909
             Project: Kafka
          Issue Type: Bug
          Components: kraft
    Affects Versions: 3.4.0
            Reporter: David Arthur
             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)