[
https://issues.apache.org/jira/browse/KAFKA-4134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15468274#comment-15468274
]
ASF GitHub Bot commented on KAFKA-4134:
---------------------------------------
GitHub user cotedm opened a pull request:
https://github.com/apache/kafka/pull/1829
KAFKA-4134: log ConnectException at WARN
Simply log the connection refused instance. If we're worried about
spamming users, I can add a flag to make sure we only log this exception once,
but the initial change is to simply log what we're given. @ijuma looks like
you were last to touch this code, would you mind having a look?
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/cotedm/kafka connectexceptiondebug
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/1829.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1829
----
commit 4ad69909b71db6b8f28b8879bfc508e86b124af8
Author: Dustin Cote <dus...@confluent.io>
Date: 2016-09-06T19:15:53Z
log ConnectException at WARN
----
> Transparently notify users of "Connection Refused" for client to broker
> connections
> -----------------------------------------------------------------------------------
>
> Key: KAFKA-4134
> URL: https://issues.apache.org/jira/browse/KAFKA-4134
> Project: Kafka
> Issue Type: Improvement
> Components: consumer, producer
> Affects Versions: 0.10.0.1
> Reporter: Dustin Cote
> Assignee: Dustin Cote
> Priority: Minor
>
> Currently, Producers and Consumers log at the WARN level if the bootstrap
> server disconnects and if there is an unexpected exception in the network
> Selector. However, we log at DEBUG level if an IOException occurs in order
> to prevent spamming the user with every network hiccup. This has the side
> effect of users making initial connections to brokers not getting any
> feedback if the bootstrap server list is invalid. For example, if one starts
> the console producer or consumer up without any brokers running, nothing
> indicates messages are not being received until the socket timeout is hit.
> I propose we be more granular and log the ConnectException to let the user
> know their broker(s) are not reachable.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
