You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Yash Mayya (Jira)" <ji...@apache.org> on 2022/08/03 14:29:00 UTC
[jira] [Commented] (KAFKA-13952) Infinite retry timeout is not working
[ https://issues.apache.org/jira/browse/KAFKA-13952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17574748#comment-17574748 ]
Yash Mayya commented on KAFKA-13952:
------------------------------------
[~jmalek] this definitely looks like a bug in the implementation of RetryWithToleranceOperator. Thanks for discovering this issue and filing a bug JIRA. I've raised a PR to fix this issue - https://github.com/apache/kafka/pull/12478
> 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
> Priority: Minor
>
> 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)