[
https://issues.apache.org/jira/browse/KAFKA-9535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Boyang Chen updated KAFKA-9535:
-------------------------------
Description:
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.
was: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.
> 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, 2.4.0, 2.5.0
> Reporter: 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)
