[
https://issues.apache.org/jira/browse/KAFKA-9535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17037954#comment-17037954
]
ASF GitHub Bot commented on KAFKA-9535:
---------------------------------------
hachikuji commented on pull request #8088: KAFKA-9535: Update metadata upon
retrying partitions for ListOffset
URL: https://github.com/apache/kafka/pull/8088
----------------------------------------------------------------
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:
us...@infra.apache.org
> Metadata not updated when consumer encounters FENCED_LEADER_EPOCH
> -----------------------------------------------------------------
>
> Key: KAFKA-9535
> URL: https://issues.apache.org/jira/browse/KAFKA-9535
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 2.3.0
> Reporter: Boyang Chen
> Assignee: Boyang Chen
> Priority: Major
>
> Inside the consumer Fetcher's handling of ListOffsetResponse, if we hit
> `FENCED_LEADER_EPOCH` on partition level, the client will blindly retry
> without refreshing the metadata, creating a stuck state as the local leader
> epoch never gets updated and constantly fails the broker check.
> The solution is to trigger metadata update upon receiving retriable errors,
> before we kick off another offset list.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
