[jira] [Updated] (KUDU-2600) Java client: improve error message when trying to connect to the web instead of RPC port

["Grant Henke (Jira)" <ji...@apache.org>]

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

Grant Henke updated KUDU-2600:
------------------------------
    Labels: beginner  (was: )

> Java client: improve error message when trying to connect to the web instead of RPC port
> ----------------------------------------------------------------------------------------
>
>                 Key: KUDU-2600
>                 URL: https://issues.apache.org/jira/browse/KUDU-2600
>             Project: Kudu
>          Issue Type: Improvement
>          Components: client, java
>    Affects Versions: 1.7.0
>            Reporter: Alexey Serbin
>            Priority: Minor
>              Labels: beginner
>
> When using Kudu Java client and specifying wrong RPC port, error messages look like the following:
> {noformat}
> org.apache.kudu.client.NoLeaderFoundException: Master config (<ip0>,<ip1>,<ip2>) has no leader. Exceptions received: org.apache.kudu.client.RecoverableException: connection disconnected,org.apache.kudu.client.RecoverableException: connection disconnected,org.apache.kudu.client.RecoverableException: connection disconnected no leader error
> {noformat}
> It would be nice to make the error message more actionable in that case.  E.g., if using Kudu C++ client the error message would be more actionable, containing the following:
> {noformat}
> ... received invalid RPC message which appears to be an HTTP response. Verify that you have specified a valid RPC port and not an HTTP port.
> {noformat}
> The relevant piece of the C++ code for that is in {{src/kudu/rpc/blocking_ops.cc}}, function {{ReceiveFramedMessageBlocking()}}.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)