Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Won't Fix
-
None
-
None
-
None
-
None
Description
Today, when a batch is expired in the accumulator, a TimeoutException is raised to the user.
It might be better the producer to retry the expired batch rather up to the configured number of retries. This is more intuitive from the user's point of view.
Further the proposed behavior makes it easier for applications like mirror maker to provide ordering guarantees even when batches expire. Today, they would resend the expired batch and it would get added to the back of the queue, causing the output ordering to be different from the input ordering.
Attachments
Issue Links
- is superceded by
-
KAFKA-5886 Introduce delivery.timeout.ms producer config (KIP-91)
- Resolved
- mentioned in
-
Page Loading...