[
https://issues.apache.org/jira/browse/HBASE-15756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15272823#comment-15272823
]
Gary Helmling commented on HBASE-15756:
---------------------------------------
We had a pluggable RpcServer back when security was first implemented, in order
to make security completely optional. What it typically meant was that patches
were only tested against the default RPC server and bugs or regressions would
show up in the non-default server due to other changes and have to be fixed up
after the fact. Let's not go back to that.
If a netty-based server shows clear gains in perf/flexibility/maintainability
over our current implementation, let's just switch to that. But of course we
can't break the wire format itself.
If we need to stabilize an implementation, do it in a branch while it is being
developed. In my opinion, having been through this, making the server
pluggable just adds complexity without adding any real value there.
I'm happy to help review a patch with some numbers behind it as well.
> Pluggable RpcServer
> -------------------
>
> Key: HBASE-15756
> URL: https://issues.apache.org/jira/browse/HBASE-15756
> Project: HBase
> Issue Type: Improvement
> Reporter: binlijin
> Assignee: binlijin
>
> 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
(v6.3.4#6332)
