[jira] [Commented] (SAMZA-610) Fail container (without send retry) when Kafka producer throws a RetriableException

["Tao Feng (JIRA)" <ji...@apache.org>]

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

Tao Feng commented on SAMZA-610:
--------------------------------

Just a question on this thread: Samza by default sets max.inflight.requests to 1 which I assume should prevent the message reordering. Why message re-ordering will happen?

> Fail container (without send retry) when Kafka producer throws a RetriableException
> -----------------------------------------------------------------------------------
>
>                 Key: SAMZA-610
>                 URL: https://issues.apache.org/jira/browse/SAMZA-610
>             Project: Samza
>          Issue Type: Bug
>            Reporter: Navina Ramesh
>
> With the new Java-based Kafka producer, we get 2 kinds of exceptions - RetriableException & Non-RetriableException.
> We have set max.retries to INT_MAX. This means that if the producer throws a RetriableException, it has already retried the send request. At the Samza level, we just have to fail the container in order to avoid re-ordering of messages. Currently, we retry from the Samza layer, which should not be necessary. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)