You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Jiangjie Qin (JIRA)" <ji...@apache.org> on 2018/07/13 16:22:00 UTC

[jira] [Assigned] (KAFKA-5886) Introduce delivery.timeout.ms producer config (KIP-91)

     [ https://issues.apache.org/jira/browse/KAFKA-5886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jiangjie Qin reassigned KAFKA-5886:
-----------------------------------

    Assignee: Yu Yang  (was: Sumant Tambe)

> 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: Yu Yang
>            Priority: Major
>
> 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
(v7.6.3#76005)