You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Bill Bejeck (Jira)" <ji...@apache.org> on 2020/10/20 17:02:00 UTC
[jira] [Updated] (KAFKA-9621) AdminClient listOffsets operation
does not respect retries and backoff
[ https://issues.apache.org/jira/browse/KAFKA-9621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bill Bejeck updated KAFKA-9621:
-------------------------------
Fix Version/s: (was: 2.7.0)
> 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
>
> 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)