[KAFKA-14909] KRaft Controllers not setting ZkMigrationReady tagged field

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.4.0
• Fix Version/s: 3.5.0
• Component/s: kraft
• Assignee: Luke Chen
• Reporter: David Arthur
• Created: 14/Apr/23 19:30
• Updated: 03/May/23 08:34
• Resolved: 03/May/23 08:34

Description

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

Issue Links

• links to: GitHub Pull Request #13631