Description
We propose adding a new timeout delivery.timeout.ms. The window of enforcement includes batching in the accumulator, retries, and the inflight segments of the batch. With this config, the user has a guaranteed upper bound on when a record will either get sent, fail or expire from the point when send returns. In other words we no longer overload request.timeout.ms to act as a weak proxy for accumulator timeout and instead introduce an explicit timeout that users can rely on without exposing any internals of the producer such as the accumulator.
See KIP-91 for more details.
Attachments
Issue Links
- supercedes
-
KAFKA-5621 The producer should retry expired batches when retries are enabled
-
- Resolved
-
- links to
(1 mentioned in)