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

Posted to issues@hbase.apache.org by "Andrew Kyle Purtell (Jira)" <ji...@apache.org> on 2022/07/01 21:45:00 UTC

[jira] [Closed] (HBASE-21957) Unify refCount of BucketEntry and refCount of hbase.nio.ByteBuff into one

     [ https://issues.apache.org/jira/browse/HBASE-21957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Kyle Purtell closed HBASE-21957.
---------------------------------------

> Unify refCount of BucketEntry and refCount of hbase.nio.ByteBuff into one
> -------------------------------------------------------------------------
>
>                 Key: HBASE-21957
>                 URL: https://issues.apache.org/jira/browse/HBASE-21957
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Zheng Hu
>            Assignee: Zheng Hu
>            Priority: Major
>             Fix For: 3.0.0-alpha-1, 2.3.0
>
>         Attachments: HBASE-21957.HBASE-21879.v1.patch, HBASE-21957.HBASE-21879.v10.patch, HBASE-21957.HBASE-21879.v11.patch, HBASE-21957.HBASE-21879.v11.patch, HBASE-21957.HBASE-21879.v2.patch, HBASE-21957.HBASE-21879.v3.patch, HBASE-21957.HBASE-21879.v4.patch, HBASE-21957.HBASE-21879.v5.patch, HBASE-21957.HBASE-21879.v6.patch, HBASE-21957.HBASE-21879.v8.patch, HBASE-21957.HBASE-21879.v9.patch, HBASE-21957.HBASE-21879.v9.patch
>
>
> After HBASE-12295, we have block with MemoryType.SHARED or MemoryType.EXCLUSIVE, the block in offheap BucketCache will be shared, and have an reference count to track its life cycle.  If no rpc reference to the shared block, then the block can be evicted. 
> while after the HBASE-21916,  we introduced an refcount for ByteBuff,  then I think we can unify the two into one.  tried to fix this when preparing patch for HBASE-21879, but seems can be different sub-task, and it won't affect the main logic of HBASE-21879,  so create a seperate one. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)