hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ramkrishna.s.vasudevan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-15756) Pluggable RpcServer
Date Mon, 08 Aug 2016 10:32:20 GMT

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

ramkrishna.s.vasudevan commented on HBASE-15756:
------------------------------------------------

[~aoxiang]
I think I got that it is for branch-1. But my point was that the pooling of the ByteBuffers
was done after the layer were the data is read from Netty. That is to answer Stack's question.
When I read that Pooling was enabled I thought the Netty's pooling itself comes into play
for process the requests. Hence went through the patch. Thank [~aoxiang].

> 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: 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, 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)

Mime
View raw message