[
https://issues.apache.org/jira/browse/HBASE-15756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15273536#comment-15273536
]
Yu Li commented on HBASE-15756:
-------------------------------
Thanks for chim in [~ghelmling]
bq. 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... making
the server pluggable just adds complexity without adding any real value there.
Understood the concerns, but maybe we could use Parameterized way to cover UT?
And it seems we already made RpcClient pluggable... One advantage of making it
pluggable may be that we could work in parallel with offheap work?
bq. If we need to stabilize an implementation, do it in a branch while it is
being developed
I see, thanks for the note sir.
bq. I'm happy to help review a patch with some numbers behind it as well.
Thanks for offering the help sir, will let you know when we're well prepared.
:-)
> 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)
