When Apache Kafka misbehaves, the cause is usually one of a handful of familiar issues. Here is how to spot and fix them fast.
The usual suspects
- Too few partitions, capping consumer parallelism
- Ignoring consumer lag until it becomes an outage
- No schema management, so producers break consumers
Commands for diagnosis
kafka-console-consumer.sh --bootstrap-server localhost:9092 --topic orders --from-beginning
kafka-consumer-groups.sh --bootstrap-server localhost:9092 --describe --group billingPrevent the repeat
- Size partitions for target consumer parallelism up front
- Monitor consumer lag and set alerts on it
- Use a Schema Registry and compatibility rules
Want senior help putting Apache Kafka to work - or a team bootcamp on it? CodeWizard runs Israel's largest DevOps community and embeds named senior engineers with a transparent hours log. Book a free consult or explore the Academy.