kafka-jira mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ismael Juma (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-5621) The producer should retry expired batches when retries are enabled
Date Tue, 25 Jul 2017 11:46:00 GMT

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

Ismael Juma commented on KAFKA-5621:
------------------------------------

[~jjkoshy], [~becket_qin], [~sutambe], what are your thoughts on the approach suggested in
this JIRA? It seems like this approach was not mentioned in KIP-91. The main advantage is
that it doesn't require a new config and it seems to be what many expect: retries apply to
any request.timeout.ms failure.

We are keen on implementing a solution for this as soon as possible as there is currently
no good solution for this problem.

> The producer should retry expired batches when retries are enabled
> ------------------------------------------------------------------
>
>                 Key: KAFKA-5621
>                 URL: https://issues.apache.org/jira/browse/KAFKA-5621
>             Project: Kafka
>          Issue Type: Bug
>            Reporter: Apurva Mehta
>             Fix For: 1.0.0
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message