You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Alexey Serbin (JIRA)" <ji...@apache.org> on 2018/10/05 18:46:00 UTC

[jira] [Created] (KUDU-2600) Java client: improve error message when trying to connect to a Web instead of RPC port

Alexey Serbin created KUDU-2600:
-----------------------------------

             Summary: Java client: improve error message when trying to connect to a 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


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
(v7.6.3#76005)