[
https://issues.apache.org/jira/browse/KAFKA-9800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17124354#comment-17124354
]
Ismael Juma commented on KAFKA-9800:
------------------------------------
For a bit more context, the plan was to add per request timeout support to
NetworkClient and migrate AdminClient to use it. I had the start of a PR
(([https://github.com/apache/kafka/pull/3503/|https://github.com/apache/kafka/pull/3503/files]),
but we then decided to go with a simpler approach that was good enough for
what the Consumer needed. Tackling that may increase the scope of this work by
quite a bit though. It may be worth checking if we can encapsulate the logic
for exponential backoff in separate classes and then use it from where retries
are handled today for the relevant clients.
And tackle the consolidation of per request timeouts in a separate JIRA.
> [KIP-580] Client Exponential Backoff Implementation
> ---------------------------------------------------
>
> Key: KAFKA-9800
> URL: https://issues.apache.org/jira/browse/KAFKA-9800
> Project: Kafka
> Issue Type: New Feature
> Reporter: Cheng Tan
> Assignee: Cheng Tan
> Priority: Major
> Labels: KIP-580
>
> In {{KafkaAdminClient}}, we will have to modify the way the retry backoff is
> calculated for the calls that have failed and need to be retried. >From the
> current static retry backoff, we have to introduce a mechanism for all calls
> that upon failure, the next retry time is dynamically calculated.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
