[jira] [Resolved] (KAFKA-13952) Infinite retry timeout is not working

["Chris Egerton (Jira)" <ji...@apache.org>]

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

Chris Egerton resolved KAFKA-13952.
-----------------------------------
    Fix Version/s: 3.4.0
       Resolution: Fixed

> Infinite retry timeout is not working
> -------------------------------------
>
>                 Key: KAFKA-13952
>                 URL: https://issues.apache.org/jira/browse/KAFKA-13952
>             Project: Kafka
>          Issue Type: Bug
>          Components: KafkaConnect
>            Reporter: Jakub Malek
>            Assignee: Yash Mayya
>            Priority: Minor
>             Fix For: 3.4.0
>
>
> The [documentation|https://github.com/apache/kafka/blob/trunk/connect/runtime/src/main/java/org/apache/kafka/connect/runtime/ConnectorConfig.java#L129] for {{errors.retry.timeout}} property says:
> {noformat}
> The maximum duration in milliseconds that a failed operation will be reattempted. The default is 0, which means no retries will be attempted. Use -1 for infinite retries.{noformat}
> But it seems that value {{-1}} is not respected by the [RetryWithToleranceOperator|https://github.com/apache/kafka/blob/trunk/connect/runtime/src/main/java/org/apache/kafka/connect/runtime/errors/RetryWithToleranceOperator.java] that simply compares elapsed time until {{startTime + errorRetryTimeout}} is exceeded.
> I was also not able to find any conversion of the raw config value before {{RetryWithToleranceOperator}} is initialized.
> I run a simple test with a connector using mocked transformation plugin that throws the {{RetriableException}} and it seems to prove my claim.
> I'm not sure if it's documentation or implementation error or maybe I've missed something.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)