🔒 Paid
Consumer Rebalance Storm
A rolling deploy is restarting consumer instances one at a time, and each individual restart is triggering a full consumer group rebalance — the whole group pauses, partitions get reassigned, and consumption resumes, only for the next restart to trigger another one. The group is spending more time rebalancing than actually processing messages, even though every individual consumer reports healthy. Diagnose the churn and stabilize the group before effective throughput collapses entirely.
- Difficulty
- Staff
- Expected Time
- ~15 min
- Category
- Messaging & Streaming
Skills
- Diagnosing rebalance churn vs. backpressure
- Static group membership and session-timeout tuning
- Deploy-strategy tradeoffs under stateful coordination
- Recognizing plausible-but-harmful mitigations
System Architecture
- Deploy Pipeline
- Health Check Service
- Consumer Group
- Kafka Topic
- Downstream Processor
This is a Pro scenario. Upgrade to Pro to unlock it.
Upgrade to ProBack to Incidents