Fault Tree Analysis Applied to Apache Kafka
summary
Applies fault tree analysis to Kafka clusters and gives concrete numbers: assumes 4% annual disk failure, 2% network, 1% hardware and OS faults, computes a single-broker failure ~12.8%, shows three brokers + three Zookeepers on SSDs reaches four nines availability, cites AWS EBS at 0.2% as an alternative, models remediation (three-day and longer) and replica rebuild rates (70 MB/s ⇒ 24 hours for 6 TB, 8 days for very large brokers) and shows when durability drops below 7 nines; diagrams and scripts on GitHub (scram / FTA-Kafka).
AI-written summary · about
chapters (6)
- 0:00Introduction to Kafka SLOs
- 3:21Why Kafka reliability matters
- 8:22Fault tree analysis basics
- 17:56Analyzing Kafka availability
- 23:23Ensuring data durability
- 27:35Latency and final thoughts
related talks
13mScaling Kafka on Kubernetes
53mDemystifying Kafka
41mUnderstanding the CAP Theorem with Apache Kafka
01h 12mRedundancy does not imply fault tolerance
38mRe-architecting Apache Kafka for the Cloud
24mMake Your Kafka Cluster Production-Ready
41mKafka as a Platform: The Ecosystem from the Ground Up
47mRunning Kafka in Kubernetes: a practical guide
