Kafka's InconsistentClusterIdException can trigger a dangerous cascade: container restart loops, log flooding, and eventually a full disk. This post walks through a real incident on Ubuntu 22.04 with Docker 24.x and Bitnami Kafka 3.1. The author explains how to check cluster IDs in ZooKeeper and Kafka logs, reset the cluster ID safely, and clean up disk space. Key takeaways include always verifying cluster ID consistency after migrations and setting log retention limits. For DevOps and SRE teams, this is a practical guide to avoid a common but painful Kafka failure mode.
A detailed case study on diagnosing Kafka cluster ID mismatches in Docker, preventing container restarts and disk exhaustion.