kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Guozhang Wang (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (KAFKA-2221) Log the entire cause which caused a reconnect in the SimpleConsumer
Date Fri, 29 Jan 2016 04:25:39 GMT

     [ https://issues.apache.org/jira/browse/KAFKA-2221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Guozhang Wang updated KAFKA-2221:
       Resolution: Fixed
    Fix Version/s:
           Status: Resolved  (was: Patch Available)

Issue resolved by pull request 138

> Log the entire cause which caused a reconnect in the SimpleConsumer
> -------------------------------------------------------------------
>                 Key: KAFKA-2221
>                 URL: https://issues.apache.org/jira/browse/KAFKA-2221
>             Project: Kafka
>          Issue Type: Improvement
>            Reporter: jaikiran pai
>            Assignee: jaikiran pai
>            Priority: Minor
>             Fix For:
>         Attachments: KAFKA-2221.patch
> 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
> {quote}
> kafka.consumer.SimpleConsumer: Reconnect due to socket error: null.
> {quote}
> It would help narrowing down the problem if the entire exception stacktrace was logged.

This message was sent by Atlassian JIRA

View raw message