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

Log the entire cause which caused a reconnect in the SimpleConsumer

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 0.9.0.1
    • Component/s: None
    • Labels:
      None

      Description

      Currently if the SimpleConsumer goes for a reconnect, it logs the exception's message which caused the reconnect. However, in some occasions the message in the exception can be null, thus making it difficult to narrow down the cause for the reconnect. An example of this can be seen in this user mailing list thread http://mail-archives.apache.org/mod_mbox/kafka-users/201505.mbox/%3CCABME_6T%2Bt90%2B-eQUtnu6R99NqRdMpVj3tqa95Pygg8KOQSNppw%40mail.gmail.com%3E

      kafka.consumer.SimpleConsumer: Reconnect due to socket error: null.

      It would help narrowing down the problem if the entire exception stacktrace was logged.

        Attachments

        1. KAFKA-2221.patch
          0.9 kB
          jaikiran pai

          Activity

            People

            • Assignee:
              jaikiran jaikiran pai
              Reporter:
              jaikiran jaikiran pai
            • Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: