You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Akhil Sabu (Jira)" <ji...@apache.org> on 2026/05/19 08:45:00 UTC
[jira] [Updated] (KAFKA-20599) Improve retry logic in KafkaStatusBackingStore with exponential backoff and retry limits
[ https://issues.apache.org/jira/browse/KAFKA-20599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Akhil Sabu updated KAFKA-20599:
-------------------------------
Reviewer: (was: Sanskar Jhajharia)
> Improve retry logic in KafkaStatusBackingStore with exponential backoff and retry limits
> ----------------------------------------------------------------------------------------
>
> Key: KAFKA-20599
> URL: https://issues.apache.org/jira/browse/KAFKA-20599
> Project: Kafka
> Issue Type: Improvement
> Components: connect
> Reporter: Akhil Sabu
> Priority: Minor
>
>
>
> The `KafkaStatusBackingStore` class contains a TODO comment at line 283 indicating that the retry logic needs improvement:
> // TODO: retry more gracefully and not forever
> if (exception instanceof RetriableException) {
> sendRetryExecutor.submit(() -> kafkaLog.send(key, value, this));
> }
>
> Currently, when a {{RetriableException}} occurs while writing status updates to Kafka, the code:
> # Retries indefinitely without any maximum attempt limit
> # Has no backoff delay between retry attempts
> # Does not implement exponential backoff to reduce load during failures
> # Can be resource-intensive and overwhelm the system during prolonged outages
--
This message was sent by Atlassian Jira
(v8.20.10#820010)