[
https://issues.apache.org/jira/browse/KAFKA-5886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guozhang Wang updated KAFKA-5886:
---------------------------------
*Reminder to the contributor / reviewer of the PR*: please note that the code
deadline for 1.0.0 is less than 2 weeks away (Oct. 4th). Please re-evaluate
your JIRA and see if it still makes sense to be merged into 1.0.0 or it could
be pushed out to 1.1.0, or be closed directly if the JIRA itself is not valid
any more, or re-assign yourself as contributor / committer if you are no longer
working on the JIRA.
> 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)
