conduktor.io ↗

retries — Kafka Producer Configuration

Setting a value greater than zero will cause the client to resend any request that fails with a potentially transient error. It is recommended to set the value to either zero or `MAX_VALUE` and use corresponding timeout parameters to control how long a client should retry a request.

Description

Setting a value greater than zero will cause the client to resend any request that fails with a potentially transient error. It is recommended to set the value to either zero or `MAX_VALUE` and use corresponding timeout parameters to control how long a client should retry a request.

Default Values by Kafka Version

Kafka VersionDefault Value
0.8.10
0.8.20
0.9.00
0.10.00
0.10.10
0.10.20
0.11.00
1.00
1.10
2.00
2.12147483647
2.22147483647
2.32147483647
2.42147483647
2.52147483647
2.62147483647
2.72147483647
2.82147483647
3.02147483647
3.12147483647
3.22147483647
3.32147483647
3.42147483647
3.52147483647
3.62147483647
3.72147483647
3.82147483647
3.92147483647
4.02147483647
4.12147483647
4.22147483647

Tuning Recommendation

ProfileRecommendedWhy
producer / throughput2147483647Keep retries at MAX_INT (default since 2.1) and rely solely on delivery.timeout.ms to bound the total retry window; manually reducing retries can cause silent data loss on transient leader elections.
producer / durability2147483647Keep retries at MAX_INT (default since 2.1) and let delivery.timeout.ms govern the total retry window; manually capping retries can cause silent data loss during transient leader elections or ISR shrinkage events that resolve within seconds.

Related Configs

acks · enable.idempotence · max.in.flight.requests.per.connection · delivery.timeout.ms · retry.backoff.ms · retry.backoff.max.ms · request.timeout.ms

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