Kafka - Consumer Groups
A Kafka consumer group is configured with cooperative rebalancing but experiences frequent full rebalances. What is a likely cause?
A Kafka consumer group is configured with cooperative rebalancing but experiences frequent full rebalances. What is a likely cause?
medium📝 Debug Q6 of 15
Step-by-Step Solution
Solution:
Step 1: Identify cause of full rebalances despite cooperative config
If the partition.assignment.strategy does not support cooperative rebalancing, full eager rebalances occur.Step 2: Rule out other options
Session timeout affects heartbeat detection, offset commits affect processing, and partition count affects parallelism but not rebalance style.Final Answer:
Using an incompatible partition.assignment.strategy with cooperative rebalancing. -> Option DQuick Check:
Full rebalance cause = A [OK]
Quick Trick: Use compatible assignment strategy for cooperative rebalancing [OK]
Common Mistakes:
- Blaming session timeout for rebalance style
- Confusing offset commits with rebalance triggers
- Assuming partition count affects rebalance type
Master "Consumer Groups" in Kafka
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Kafka Quizzes