kafka-jira mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tommy Becker (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-5886) Introduce delivery.timeout.ms producer config (KIP-91)
Date Fri, 29 Sep 2017 19:52:00 GMT

    [ https://issues.apache.org/jira/browse/KAFKA-5886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16186303#comment-16186303
] 

Tommy Becker commented on KAFKA-5886:
-------------------------------------

Is this still on track for 1.0? We just hit an issue with records expiring in the accumulator
when the producer is heavily loaded. The current behavior of expiring batches even on partitions
that are making progress is quite unintuitive, as is the current fix.

> 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)

Mime
View raw message