[
https://issues.apache.org/jira/browse/KAFKA-4134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17001172#comment-17001172
]
ASF GitHub Bot commented on KAFKA-4134:
---------------------------------------
cotedm commented on pull request #1829: KAFKA-4134: log ConnectException at WARN
URL: https://github.com/apache/kafka/pull/1829
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> 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
(v8.3.4#803005)
