Minimum number of messages per topic+partition in the local consumer queue.
Maximum time the broker may wait to fill the response with fetch.min.bytes.
Maximum time a broker socket operation may block.
A lower value improves responsiveness at the expense of slightly higher CPU usage.
How long to postpone the next fetch request for a topic+partition in case of a fetch error.
Maximum number of messages batched in one MessageSet.
Maximum time, in milliseconds, for buffering data on the producer queue.
Compression codec to use for compressing message sets: none, gzip or snappy.
Maximum time a broker socket operation may block.
A lower value improves responsiveness at the expense of slightly higher CPU usage.
This field indicates how many acknowledgements the leader broker must receive from ISR (in-sync-replicas) brokers before responding to the request: 0=broker does not send any response, 1=broker will wait until the data is written to local log before sending a response, -1=broker will block until message is committed by all in sync replicas (ISRs) or broker's in.sync.replicas setting before sending response. 1=Only the leader broker will need to ack the message.
A batch is ready when one of the following is true:
In general, more batching results in:
acks | Throughput | Latency | Durability |
---|---|---|---|
0 | high | low | No guarantee |
1 | medium | medium | only leader |
-1 | low | high | ISR |