enable.idempotence — Kafka Producer Configuration
When set to 'true', the producer will ensure that exactly one copy of each message is written in the stream. If 'false', producer retries due to broker failures, etc.
Description
When set to 'true', the producer will ensure that exactly one copy of each message is written in the stream. If 'false', producer retries due to broker failures, etc., may write duplicates of the retried message in the stream. Note that enabling idempotence requires max.in.flight.requests.per.connection to be less than or equal to 5 (with message ordering preserved for any allowable value), retries to be greater than 0, and acks must be 'all'.
Default Values by Kafka Version
| Kafka Version | Default Value |
|---|---|
| 0.11.0 | false |
| 1.0 | false |
| 1.1 | false |
| 2.0 | false |
| 2.1 | false |
| 2.2 | false |
| 2.3 | false |
| 2.4 | false |
| 2.5 | false |
| 2.6 | false |
| 2.7 | false |
| 2.8 | false |
| 3.0 | true |
| 3.1 | true |
| 3.2 | true |
| 3.3 | true |
| 3.4 | true |
| 3.5 | true |
| 3.6 | true |
| 3.7 | true |
| 3.8 | true |
| 3.9 | true |
| 4.0 | true |
| 4.1 | true |
| 4.2 | true |
Tuning Recommendation
| Profile | Recommended | Why |
|---|---|---|
| producer / throughput | true | Keep idempotence enabled (default since 3.0): it adds zero throughput cost while preventing duplicate records on retries, and it is required for exactly-once semantics; disabling it only saves overhead if acks=0 is set. |
| producer / latency | false | Disabling idempotence is required when acks=1 is set; it also removes the PID assignment handshake at startup and the sequence-number tracking overhead per batch, shaving a few microseconds per ProduceRequest on the hot path. |
| producer / durability | true | Idempotent producer assigns a monotonically increasing sequence number per partition per PID; the broker deduplicates any retry of the same batch within the same producer epoch, guaranteeing exactly-once per partition even when the network causes a resend. Default since Kafka 3.0. |
Related Configs
acks · retries · max.in.flight.requests.per.connection · transactional.id
Manage Kafka configs across all your clusters with Conduktor Console — view, compare, and update configurations in one place.