What is a rebalance storm, and how do you keep consumers stable?
PICTURE THIS: SQL JOIN
Simple meaning
When members join or miss heartbeats, Kafka revokes partitions and the group stops processing during the rebalance.
WHY — Kafka instead of guessing?
Why interviewers care about Kafka:
who only read docs from people who shipped.
and tied to Backend work.
Name the idea, why it exists, then one short example.
End with when you use it and one common pitfall.
STEPS — What happens step by step?
Before you speak the answer, walk the interviewer through these steps:
- 1When members join or
miss heartbeats, Kafka revokes partitions and the group stops processing during the rebalance.
- 2Frequent deploys, long GC,
and max.poll.interval too short cause join/leave flaps.
- 3Raise session timeouts carefully,
process records without blocking the poll loop forever, and use incremental cooperative rebalancing.
- 4Give an example
One tiny concrete case you can say aloud.
- 5Common mistake
What juniors usually get wrong.
- 6Close
When you pick this over the alternative.
EXAMPLE — See it in action
Here's a short line you can speak, broken into clear beats:
Note: Adapt this scaffold to your own project — keep it under 60–90 seconds.
Key takeaway
When members join or miss heartbeats, Kafka revokes partitions and the group stops processing during the rebalance. Frequent deploys, long GC, and max.poll.interval too short cause join/leave flaps.