[
https://issues.apache.org/jira/browse/HBASE-15756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15400386#comment-15400386
]
binlijin commented on HBASE-15756:
----------------------------------
First let me try to explain Netty's Thread Model first:
Netty's NioWork read request from channel, decode into Call and handoff it to
HBase Handlers via Queue, when HBase Handlers done all the work, it will
handoff the result to the channel's WriteBufferQueue, then Netty's NioWork
batch write the result to the client.
So i think the big different Between the NettyRpcServer with the current
RpcServer is the write response.
@Jurriaan Mous, if there is wrong, please correct me.
> 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
> Attachments: NettyRpcServer.patch, NettyRpcServer_forperf.patch,
> gets.png, idle.png, queue.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
(v6.3.4#6332)
