conduktor.io ↗

replica.fetch.max.bytes — Kafka Broker Configuration

The number of bytes of messages to attempt to fetch for each partition. This is not an absolute maximum, if the first record batch in the first non-empty partition of the fetch is larger than this value, the record batch will still be returned to ensure that progress can be made.

Description

The number of bytes of messages to attempt to fetch for each partition. This is not an absolute maximum, if the first record batch in the first non-empty partition of the fetch is larger than this value, the record batch will still be returned to ensure that progress can be made. The maximum record batch size accepted by the broker is defined via message.max.bytes (broker config) or max.message.bytes (topic config).

Default Values by Kafka Version

Kafka VersionDefault Value
0.8.01024 * 1024
0.8.11024 * 1024
0.8.21024 * 1024
0.9.01048576
0.10.01048576
0.10.11048576
0.10.21048576
0.11.01048576
1.01048576
1.11048576
2.01048576
2.11048576
2.21048576
2.31048576
2.41048576
2.51048576
2.61048576 (1 mebibyte)
2.71048576 (1 mebibyte)
2.81048576 (1 mebibyte)
3.01048576 (1 mebibyte)
3.11048576 (1 mebibyte)
3.21048576 (1 mebibyte)
3.31048576 (1 mebibyte)
3.41048576 (1 mebibyte)
3.51048576 (1 mebibyte)
3.61048576 (1 mebibyte)
3.71048576 (1 mebibyte)
3.81048576 (1 mebibyte)
3.91048576 (1 mebibyte)
4.01048576 (1 mebibyte)
4.11048576 (1 mebibyte)
4.21048576 (1 mebibyte)

Tuning Recommendation

ProfileRecommendedWhy
broker / throughput10485760Increasing the per-fetch-request byte limit to 10MB allows follower fetchers to pull more data per round-trip, reducing replication lag at high produce rates. The default 1MB cap causes replication round-trips to dominate at >100MB/s ingestion.

Related Configs

num.replica.fetchers · message.max.bytes · replica.socket.receive.buffer.bytes

Manage Kafka configs across all your clusters with Conduktor Console — view, compare, and update configurations in one place.