[
https://issues.apache.org/jira/browse/KAFKA-10223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17174223#comment-17174223
]
Rajini Sivaram commented on KAFKA-10223:
----------------------------------------
[~dongjoon] This is not a 2.6.0 issue, ReplicaNotAvailable has always been
non-retriable. This turned out to be a bigger issue in non-Java consumers since
fetch-from-follower was introduced in 2.4.0. Java consumers always handled
this case correctly and were not affected.
> ReplicaNotAvailableException must be retriable to handle reassignments
> ----------------------------------------------------------------------
>
> Key: KAFKA-10223
> URL: https://issues.apache.org/jira/browse/KAFKA-10223
> Project: Kafka
> Issue Type: Bug
> Components: clients
> Reporter: Rajini Sivaram
> Assignee: Rajini Sivaram
> Priority: Critical
> Fix For: 2.6.0
>
>
> ReplicaNotAvailableException should be a retriable `InvalidMetadataException`
> since consumers may throw this during reassignments.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
