42 Ways ZooKeeper Removal Improves Apache Kafka
Feb 18, 2021Yeva Byzek

Summary
This post details the benefits of removing ZooKeeper from Apache Kafka, focusing on the simplification of administration, capacity planning, performance, monitoring, and troubleshooting. It highlights specific tasks that can be stopped, such as operating a separate distributed system, administering additional servers, managing separate security configurations, and dealing with ZooKeeper-specific tuning parameters and maintenance. The post also emphasizes performance improvements due to local metadata storage in brokers and the elimination of O(N) costs for topic operations. It provides concrete examples of how client and tool configurations will change with the removal of ZooKeeper.
More from the Kafka KRaft Migration trail
- Announcing Confluent Platform 8.3: Powerful Apache Flink® SQL operations, Easier KRaft Migrations, Expanded Monitoring and more
- Apache Kafka 4.3 released: 25 KIPs, Kafka Streams, Share Group Controls, Broker Isolation, and more
- Introducing Confluent Platform 8.2: Queues for Kafka & Flink SQL
- Migrate From Hosted Kafka to Confluent Cloud in the KRaft Era
- Apache Kafka 4.1 Release: New Features & Upgrade Guide