[jira] [Updated] (KAFKA-9558) getListOffsetsCalls doesn't update node in case of leader change

["Jason Gustafson (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/KAFKA-9558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason Gustafson updated KAFKA-9558:
-----------------------------------
    Affects Version/s:     (was: 2.5.0)

> getListOffsetsCalls doesn't update node in case of leader change
> ----------------------------------------------------------------
>
>                 Key: KAFKA-9558
>                 URL: https://issues.apache.org/jira/browse/KAFKA-9558
>             Project: Kafka
>          Issue Type: Bug
>          Components: admin
>            Reporter: Sanjana Kaundinya
>            Assignee: Sanjana Kaundinya
>            Priority: Critical
>             Fix For: 2.5.0
>
>
> As seen here:
> [https://github.com/apache/kafka/blob/trunk/clients/src/main/java/org/apache/kafka/clients/admin/KafkaAdminClient.java#L3810]
> In handling the response in the `listOffsets` call, if there are errors in the topic partition that require a metadata refresh, it simply passes the call object as `this`. This produces incorrect behavior if there was a leader change, because the call object never gets its leader node updated. This will result in a tight loop of list offsets being called to the same old leader and not resulting in offsets, even though the metadata was correctly updated.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)