Kafka - Performance Tuning
A consumer is experiencing low throughput despite high
max.poll.records. Which configuration might cause this?A consumer is experiencing low throughput despite high max.poll.records. Which configuration might cause this?
medium📝 Debug Q7 of 15
Step-by-Step Solution
Solution:
Step 1: Analyze max.poll.records and fetch.max.bytes relation
max.poll.records limits records per poll, but fetch.max.bytes limits total data size fetched.Step 2: Effect of low fetch.max.bytes
If fetch.max.bytes is too low, consumer cannot fetch large batches even if max.poll.records is high, reducing throughput.Final Answer:
fetch.max.bytes set too low, limiting batch size. -> Option BQuick Check:
fetch.max.bytes limits data size per fetch [OK]
Quick Trick: Low fetch.max.bytes blocks large batch fetches [OK]
Common Mistakes:
MISTAKES- Confusing auto commit settings with throughput
- Assuming session timeout affects fetch size
- Ignoring fetch.max.bytes impact on batch size
Master "Performance Tuning" in Kafka
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Kafka Quizzes