[
https://issues.apache.org/jira/browse/KUDU-1771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15810158#comment-15810158
]
Todd Lipcon commented on KUDU-1771:
-----------------------------------
Yea, I think that we should make the error message correct based on the actual
underlying error. Not sure if passing different string errors is the solution,
or if there is some way to get Netty to pass up the underlying socket error or
some kind of error code. [~jdcryans] might know better
> Java client "connection refused" errors logged as "connection reset"
> --------------------------------------------------------------------
>
> Key: KUDU-1771
> URL: https://issues.apache.org/jira/browse/KUDU-1771
> Project: Kudu
> Issue Type: Improvement
> Components: client
> Affects Versions: 1.1.0
> Reporter: Todd Lipcon
>
> When the Java client tries to connect to a server which is down, it generates
> an error string like: org.apache.kudu.client.RecoverableException: [Peer Kudu
> Master - vd0340.halxg.cloudera.com:7051] Connection reset
> This makes it sound like it connected and got disconnected, when in fact that
> host was not listening at all. This misleads the user when they try to
> troubleshoot the issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
