conduktor.io ↗

max.decompressed.message.bytes — Kafka Broker Configuration

The maximum decompressed size, in bytes, of a single record the broker will accept; larger records are rejected with an InvalidRecordException. It is enforced where the broker decompresses records: produce validation of compressed batches, log compaction, and offset lookups by timestamp or max timestamp against the local log or remote storage

Description

The maximum decompressed size, in bytes, of a single record the broker will accept; larger records are rejected with an InvalidRecordException. It is enforced where the broker decompresses records: produce validation of compressed batches, log compaction, and offset lookups by timestamp or max timestamp against the local log or remote storage. Unlike max.message.bytes, which bounds the compressed batch on the wire, this bounds the decompressed size of an individual record. Lowering it below the size of already-stored records makes compaction and timestamp offset lookups of affected partitions fail until it is raised again. The default imposes no limit beyond the largest record the broker could allocate anyway; set a smaller value to enforce a per-record cap. This can be set per topic with the topic level max.decompressed.message.bytes config.

Default Values by Kafka Version

ComponentKafka version lineDocumented default
Broker4.42147483639
topic4.42147483639
Manage Kafka configs across all your clusters with Conduktor Console — view, compare, and update configurations in one place.