[
https://issues.apache.org/jira/browse/KAFKA-9621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17217775#comment-17217775
]
Bill Bejeck commented on KAFKA-9621:
------------------------------------
As part of the 2.7.0 release process, I'm clearing the fix version field. When
we have a PR for this we can set the fix version at that point.
> AdminClient listOffsets operation does not respect retries and backoff
> ----------------------------------------------------------------------
>
> Key: KAFKA-9621
> URL: https://issues.apache.org/jira/browse/KAFKA-9621
> Project: Kafka
> Issue Type: Bug
> Components: admin
> Reporter: Sanjana Kaundinya
> Assignee: Cheng Tan
> Priority: Major
> Fix For: 2.7.0
>
>
> Similar to https://issues.apache.org/jira/browse/KAFKA-9047, currently the
> {{listOffsets}} operation doesn't respect the configured retries and backoff
> for a given call.
> For example, the code path could go like so:
> 1) Make a metadata request and schedule subsequent list offsets calls
> 2) Metadata error comes back with {{InvalidMetadataException}}
> 3) Go back to 1
> The problem here is that the state is not preserved across calls. We loose
> the information regarding how many tries the call has been tried and how far
> out we should schedule the call to try again. This could lead to a tight
> retry loop and put pressure on the brokers.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
