[
https://issues.apache.org/jira/browse/KAFKA-9535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Gustafson resolved KAFKA-9535.
------------------------------------
Fix Version/s: 2.4.1
2.3.2
2.5.0
Resolution: Fixed
> 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
> Fix For: 2.5.0, 2.3.2, 2.4.1
>
>
> 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)
