Uploaded image for project: 'Kafka'
  1. Kafka
  2. KAFKA-2020

I expect ReplicaNotAvailableException to have proper Javadocs

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Open
    • Major
    • Resolution: Unresolved
    • None
    • None
    • consumer
    • None

    Description

      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?

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. SAMZA-592 getSystemStreamMetadata loops forever when it receives bad metadata

          • Major - Major loss of function.
          • Resolved

          Activity

            People

              nehanarkhede Neha Narkhede
              criccomini Chris Riccomini
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated: