[
https://issues.apache.org/jira/browse/KAFKA-5886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16187976#comment-16187976
]
Tommy Becker commented on KAFKA-5886:
-------------------------------------
Thanks for the response. Though the KIP may be an improvement, I think this
behavior where sends to a perfectly functioning cluster are dropped is clearly
a bug, and I'd argue a major one. We have a use case where we are reading from
a local file and producing the records to Kafka and even with
{{request.timeout.ms = 120000}} and {{max.in.flight.requests.per.connnection =
1}} it is still dropping records.
> Introduce delivery.timeout.ms producer config (KIP-91)
> ------------------------------------------------------
>
> Key: KAFKA-5886
> URL: https://issues.apache.org/jira/browse/KAFKA-5886
> Project: Kafka
> Issue Type: Improvement
> Components: producer
> Reporter: Sumant Tambe
> Assignee: Sumant Tambe
> Fix For: 1.0.0
>
>
> 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|https://cwiki.apache.org/confluence/display/KAFKA/KIP-91+Provide+Intuitive+User+Timeouts+in+The+Producer]
> for more details.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
