You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Enis Soztutar (JIRA)" <ji...@apache.org> on 2016/11/09 00:15:58 UTC

[jira] [Commented] (HBASE-17051) libhbase++: implement RPC connection management

    [ https://issues.apache.org/jira/browse/HBASE-17051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15649287#comment-15649287 ] 

Enis Soztutar commented on HBASE-17051:
---------------------------------------

Indeed. The idea is to follow the NettyRpcClient/AbstractRpcClient model to build the corresponding interfaces and implementation in the C++ land. The RPC client will share the same kind of low level responsibilities in terms of handling sockets, tracking outgoing RPCs via Calls, timeouts and IPC / Codec encodings. This layer will not know anything about higher level retries, and user-level requests (Get, Put, etc). Those will be build on top of this layer later following the AsyncTable model.  

> libhbase++: implement RPC connection management
> -----------------------------------------------
>
>                 Key: HBASE-17051
>                 URL: https://issues.apache.org/jira/browse/HBASE-17051
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Xiaobing Zhou
>            Assignee: Xiaobing Zhou
>
> This proposes building RPC connection management layer, which supports the equivalent functions resides in RpcConnection.java. Specifically, handler/pipeline concepts will be used for implementation, similar to NettyRpcConnection in java side.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)