You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Zheng Hu (JIRA)" <ji...@apache.org> on 2019/02/16 12:10:00 UTC

[jira] [Commented] (HBASE-21916) Abstract an ByteBuffAllocator to allocate/free ByteBuffer in ByteBufferPool

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

Zheng Hu commented on HBASE-21916:
----------------------------------

Patch.v2 :  do not expose the ByteBufferPool to RpcServer again,  we can just use the ByteBufAllocator in the upper layer. 

> Abstract an ByteBuffAllocator to allocate/free ByteBuffer in ByteBufferPool
> ---------------------------------------------------------------------------
>
>                 Key: HBASE-21916
>                 URL: https://issues.apache.org/jira/browse/HBASE-21916
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Zheng Hu
>            Assignee: Zheng Hu
>            Priority: Major
>             Fix For: 3.0.0, 2.2.0, 2.3.0, 2.1.4
>
>         Attachments: HBASE-21916.v1.patch, HBASE-21916.v2.patch
>
>
> Now  our read/write path allocate ByteBuffer from the ByteBufferPool, but we need consider the minSizeForReservoirUse for better utilization, those allocate/free api are some static methods,  not so good to use. 
> For HBASE-21879,  we need an universal ByteBuffer allocator to manage all the ByteBuffers through the entire read path, so create this issue. 
> Will upload a patch to abstract an ByteBufAllocator.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)