Why ZooKeeper Was Replaced with KRaft - The Log of All Logs | Confluent Why Replace ZooKeeper with Kafka Raft - The Log of All Logs

This post details the rationale for replacing ZooKeeper with KRaft for Kafka metadata management. It explains the scalability limitations of the old controller design, particularly during broker shutdowns and controller failovers, and the inherent challenges of using ZooKeeper as a metadata store. The post then introduces KRaft as a solution, explaining the concept of a metadata log, the benefits of using quorum replication (Raft algorithm) over primary-backup, and the leader election protocol within KRaft.