You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "zhangduo (JIRA)" <ji...@apache.org> on 2015/04/15 02:39:59 UTC
[jira] [Commented] (HBASE-13467) Prototype using GRPC as IPC
mechanism
[ https://issues.apache.org/jira/browse/HBASE-13467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14495447#comment-14495447 ]
zhangduo commented on HBASE-13467:
----------------------------------
Nice try!
Two things.
1. Wire compatibility. gRPC is based on HTTP/2, and the old rpc is based on raw TCP. If we can not keep compatibility at the protocol level, then we should find other ways to let people use old client communicate with new server.
2. Secure HBase. gRPC is based on HTTP/2, so I'm not worried about the kerberos authentication part. But security is a big system, a little change here may require large change there. It maybe a big project.
Thanks.
> Prototype using GRPC as IPC mechanism
> -------------------------------------
>
> Key: HBASE-13467
> URL: https://issues.apache.org/jira/browse/HBASE-13467
> Project: HBase
> Issue Type: Improvement
> Components: API
> Affects Versions: 2.0.0
> Reporter: Louis Ryan
> Priority: Minor
>
> GRPC provide an RPC layer for protocol buffers on top of Netty 4/5. This could be used to replace the current internal implementation.
> GRPC supports some advanced features like streaming, async, flow-control, cancellation & timeout which might be useful
> Will prototype on GitHub here if folks are interested
> https://github.com/louiscryan/hbase
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)