Bird
0
0

A Kafka consumer is configured with max.poll.records=1000 but only 100 records are returned per poll. What could be a likely cause?

medium📝 Debug Q6 of 15
Kafka - Performance Tuning
A Kafka consumer is configured with max.poll.records=1000 but only 100 records are returned per poll. What could be a likely cause?
AConsumer group has too many members.
BThe broker has fewer records available in the partitions.
Cfetch.min.bytes is set to zero.
Dmax.poll.records is set too high causing errors.
Step-by-Step Solution
Solution:
  1. Step 1: Understand max.poll.records effect

    This setting is a maximum limit; actual records returned depend on availability.
  2. Step 2: Reason about fewer records returned

    If broker partitions have fewer than 1000 records, consumer returns only available records.
  3. Final Answer:

    The broker has fewer records available in the partitions. -> Option B
  4. Quick Check:

    max.poll.records limits max, not guarantees count [OK]
Quick Trick: max.poll.records caps but doesn't guarantee record count [OK]
Common Mistakes:
  • Assuming max.poll.records causes errors if high
  • Confusing fetch.min.bytes with record count
  • Blaming consumer group size for record count

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Kafka Quizzes