[
https://issues.apache.org/jira/browse/KUDU-1771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15809026#comment-15809026
]
Jun He commented on KUDU-1771:
------------------------------
[~tlipcon]
Do you mean we just simply change "Connection reset" in cleanup() and sendRpc()
methods at TableClient class to "Connection refused"?
I think there is also a chance that "connection reset" or other situations that
connection closed happen. We can pass a string parameter instead of Channel to
cleanup() to allow a caller to customize the error message.
> 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)
