You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Wenjun Zhu (Jira)" <ji...@apache.org> on 2021/04/19 09:49:00 UTC

[jira] [Created] (HBASE-25789) Other protobuf services, other than ClientService, cannot be invoked with RpcClient

Wenjun Zhu created HBASE-25789:
----------------------------------

             Summary: Other protobuf services, other than ClientService, cannot be invoked with RpcClient
                 Key: HBASE-25789
                 URL: https://issues.apache.org/jira/browse/HBASE-25789
             Project: HBase
          Issue Type: Bug
          Components: native-client
    Affects Versions: 2.4.2
            Reporter: Wenjun Zhu


I'd like to invoke a coprocessor with RpcClient, and I find the service_name in function RpcSerde::Header() has been hard coded, and when I change the service_name to another one, the call failed.


Before I change the service_name, I get the following error message:
{noformat}
# ./adamas-echo-test 
/usr/src/hbase/hbase-native-client/src/test/adamas-echo-test.cc:83: Failure
Failed
Failed because: N5hbase15RemoteExceptionE: /172.17.0.4:16000 is unable to read call parameter from client 172.17.0.4;
java.lang.UnsupportedOperationException: adamasEcho,
Shouldn't get here, exception is not expected for RPC adamasEcho.{noformat}

As I look into the hbase server, I find the service name is ClientService, which is not what I expected.

then I hard code the "ClientService" to my own service, i.e. the service name in my own .proto file, by changing the INTERFACE macro.
but when I connect to the hbase server, it reset the connection immediately, showing:
{noformat}
# ./adamas-echo-test 
/usr/src/hbase/hbase-native-client/src/test/adamas-echo-test.cc:83: Failure
Failed
Failed because: N5hbase11IOExceptionE: Connection closed to server:172.17.0.4:16000,
Shouldn't get here, exception is not expected for RPC adamasEcho.{noformat}
and I look into the wingle library, I find the errno is 104, which means 'Connection reset by peer'.

So what is the problem?
Thank you!



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