[
https://issues.apache.org/jira/browse/KAFKA-9558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17040245#comment-17040245
]
ASF GitHub Bot commented on KAFKA-9558:
---------------------------------------
hachikuji commented on pull request #8119: KAFKA-9558: Fixing retry logic for
getListOffsetsCalls
URL: https://github.com/apache/kafka/pull/8119
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> 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
> Affects Versions: 2.5.0
> Reporter: Sanjana Kaundinya
> Assignee: Sanjana Kaundinya
> Priority: Critical
>
> 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)
