[KAFKA-14304] ZooKeeper to KRaft Migration

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Assignee: David Arthur
• Reporter: David Arthur
• Created: 14/Oct/22 17:56
• Updated: 09/Aug/24 22:39
• Resolved: 09/Aug/24 22:30

Description

Top-level JIRA for KIP-866

Issue Links

• is a parent of: KAFKA-14859 Support SCRAM ZK to KRaft Migration
• is related to: KAFKA-14698 Received request api key LEADER_AND_ISR which is not enabled
• is related to: KAFKA-14692 Issues in Zookeeper to KRaft migration docs
• links to: GitHub Pull Request #12928
• links to: GitHub Pull Request #13103
• mentioned in: Page Loading...

Sub-Tasks

• Add support for ZK migration multi-ops transaction: Resolved
• Add Records, RPCs and Configs for KIP-866: Resolved
• ZK brokers register with KRaft during migration: Resolved
• API forwarding support in ZkBrokers during KRaft migration: Resolved
• RPC Handler to ZkBrokers from KRaft Controller: Resolved
• Zk to KRaft migration state machine in KRaft controller: Resolved
• Initialize KRaft with arbitrary epoch: Resolved
• Controlled shutdown for ZK brokers during migration: Resolved
• ZK broker should not send epoch during registration: Resolved
• Don't startup in migration mode if an authorizer is enabled: Resolved
• Migrate ZK ACLs to KRaft: Resolved
• KRaft Controller shouldn't allow metadata updates before migration starts: Resolved
• ZK migration cannot start if a ZK controller was not previously elected: Resolved
• Handle KRaft snapshots in dual-write mode: Resolved
• Fix overly large record batches in ZkMigrationClient: Resolved
• KRaft Controllers not setting ZkMigrationReady tagged field: Resolved
• KRaft controller sending ZK controller RPCs to KRaft brokers: Resolved
• Only expose ZkMigrationState metric if metadata.version supports it: Resolved
• Additional ZK migration metrics: Resolved