KIP-866 — ZooKeeper to KRaft Migration

Accepted Kafka 3.4 KRaft

Defines the migration path and new broker/controller APIs to move a Kafka cluster from ZooKeeper-based metadata to KRaft quorum without partition availability impact, writing metadata to both stores simultaneously during the bridge period to allow rollback. Completing KIP-500 required a concrete, reversible migration procedure since running ZooKeeper in production clusters has significant operational overhead and single-point-of-failure concerns.

Protocol Impact

BrokerRegistration · LeaderAndIsr · StopReplica · UpdateMetadata · Metadata · ApiVersions

Details