[
https://issues.apache.org/jira/browse/KAFKA-9535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17034172#comment-17034172
]
ASF GitHub Bot commented on KAFKA-9535:
---------------------------------------
abbccdda commented on pull request #8088: KAFKA-9535: Update metadata upon
receiving FENCED_LEADER_EPOCH in ListOffset
URL: https://github.com/apache/kafka/pull/8088
Today if we attempt to list offsets with a fenced leader epoch, consumer
will infinitely retry without updating the metadata. The fix is to trigger the
metadata update call when we see `FENCED_LEADER_EPOCH`, even as partial failure.
`UNKNOWN_LEADER_EPOCH`, on the other hand, indicates a metadata staleness on
broker side, so consumer don't have to update metadata.
### Committer Checklist (excluded from commit message)
- [ ] Verify design and implementation
- [ ] Verify test coverage and CI build status
- [ ] Verify documentation (including upgrade notes)
----------------------------------------------------------------
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, 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
