You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@kafka.apache.org by "Chris Riccomini (JIRA)" <ji...@apache.org> on 2015/03/13 17:44:39 UTC

[jira] [Created] (KAFKA-2020) I expect ReplicaNotAvailableException to have proper Javadocs

Chris Riccomini created KAFKA-2020:
--------------------------------------

             Summary: 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)