[
https://issues.apache.org/jira/browse/KAFKA-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14361952#comment-14361952
]
Jay Kreps commented on KAFKA-2020:
----------------------------------
Yeah we need to just fix that. I actually strongly suspect our own java clients
have that bug, too right? Their exception handling has a set of know errors
that get handled and then a catch-all throw for any other errors, which, in my
opinion is the best way to do error handling in the clients. [~junrao],
[~nehanarkhede] do you guys have any context on how we ended up with this?
> I expect ReplicaNotAvailableException to have proper Javadocs
> -------------------------------------------------------------
>
> Key: KAFKA-2020
> URL: https://issues.apache.org/jira/browse/KAFKA-2020
> Project: Kafka
> Issue Type: Bug
> Components: consumer
> Reporter: Chris Riccomini
> Assignee: Neha Narkhede
>
> It looks like ReplicaNotAvailableException was copy and pasted from
> LeaderNotAvailable exception. The Javadocs were never changed. This means
> that users think that ReplicaNotAvailableException signifies leaders are not
> available. This is very different from, "I can ignore this exception," which
> is what the Kafka protocol docs say to do with ReplicaNotAvailableException.
> Related: what's the point of ReplicaNotAvailableException if it's supposed to
> be ignored?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
