Which setting controls how many records to receive per poll request?

Which setting controls how many records to receive per poll request?

• A. fetch.min.bytes
• B. max.partition.fetch.bytes
• C. fetch.max.bytes
• D. max.poll.records

Answer: (D)

The key idea is how many records the consumer returns in a single poll call. The setting that controls this is max.poll.records. It determines the maximum number of records the consumer will deliver to your code in one poll invocation. If more records are available, they’ll be returned in subsequent polls; if fewer are available, you’ll get what’s there up to the limit. This is about the number of records per poll (a processing batch), not about bytes or how much data is fetched from the broker. The other options relate to how much data, in bytes, the broker can fetch or return per request (fetch.min.bytes, fetch.max.bytes, max.partition.fetch.bytes) and don’t constrain the per-poll record count.

The key idea is how many records the consumer returns in a single poll call. The setting that controls this is max.poll.records. It determines the maximum number of records the consumer will deliver to your code in one poll invocation. If more records are available, they’ll be returned in subsequent polls; if fewer are available, you’ll get what’s there up to the limit.

This is about the number of records per poll (a processing batch), not about bytes or how much data is fetched from the broker. The other options relate to how much data, in bytes, the broker can fetch or return per request (fetch.min.bytes, fetch.max.bytes, max.partition.fetch.bytes) and don’t constrain the per-poll record count.