Why this matters
- VaultCommerce on-call resolves 80% of Kafka pages with five playbooks.
- Start with consumer lag vs broker health — different fixes.
- Recent deploy correlation cuts MTTR in half.
- This article is the capstone for production module.
Incident reported
High lag?Scale consumers
Broker down?Check ISR
Disk full?Retention / capacity
Consumer lag playbook
- Is lag all partitions or one? (skew → hot key). 2) Consumer count vs partitions? 3) Handler slow? Check DB traces. 4) Producer surge? Check ingress rate. VaultCommerce scales consumers first, optimizes SQL second, adds partitions last.
Key points
- Symptom clustering — lag + rebalance often = slow poll
- Partition skew — single partition lagging implicates key distribution
- URP — under-replicated partitions need broker recovery
- Disk full — segment delete cannot run if disk 100%
- Deploy correlation — check release timeline first
The rest of this guide is part of Pro
Free covers every fresher guide in full. Pro unlocks Senior, Staff and Architect guides across every track.
Still to come · 2 sections
- Broker and disk playbook
- VaultCommerce rollout checklist
Test yourself
Answer these before moving on — recall is what makes it stick.