hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "binlijin (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-15756) Pluggable RpcServer
Date Tue, 13 Dec 2016 02:22:58 GMT

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

binlijin commented on HBASE-15756:

The current RpcServer is complicated, it support plain data/security/encryption data...
We only use plain data, do not use security/encryption. I think it need time to stabilize
the Netty4RpcServer with all function and do not break the wire format. And i think make RpcServer
pluggable can make it easy to implement Netty4RpcServer and switch from RpcServer to Netty4RpcServer.
When Netty4RpcServer is stabile than we can delete the current RpcServer.

> Pluggable RpcServer
> -------------------
>                 Key: HBASE-15756
>                 URL: https://issues.apache.org/jira/browse/HBASE-15756
>             Project: HBase
>          Issue Type: Improvement
>          Components: Performance, rpc
>            Reporter: binlijin
>            Assignee: binlijin
>            Priority: Critical
>             Fix For: 2.0.0
>         Attachments: Cluster_total_QPS.png, MultiResponder.branch-1.patch, MultiResponder.master.patch,
Netty4RpcServer_forperf.patch, NettyRpcServer.patch, NettyRpcServer_forperf.patch, PooledByteBufAllocator.patch,
PooledByteBufAllocator2.patch, gc.png, gets.png, gets.png, idle.png, patched.vs.patched_and_cached.vs.no_patch.png,
> Current we use a simple RpcServer, and can not configure and use other implementation.This
issue is to make the RpcServer pluggable, so we can make other implementation for example
netty rpc server. Patch will upload laterly

This message was sent by Atlassian JIRA

View raw message