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

Anoop Sam John updated HBASE-15786:
-----------------------------------
    Release Note: Added a new config 
hbase.regionserver.offheap.global.memstore.size using which one can specify the 
global off heap limit that all memstores can use.  When this config is in MSLAB 
should be turned ON and we will use the entire size for the MSLAB pool. It will 
make off heap chunks and pool then. It will behave as if we are working with 
off heap memstores.  When this config is having a valid value and MSLAB is 
turned OFF, the system will just ignore the offheap size and continue to use 
global max heap space % for memstores and work with on heap memstores.

> Create DBB backed MSLAB pool
> ----------------------------
>
>                 Key: HBASE-15786
>                 URL: https://issues.apache.org/jira/browse/HBASE-15786
>             Project: HBase
>          Issue Type: Sub-task
>          Components: regionserver
>            Reporter: ramkrishna.s.vasudevan
>            Assignee: Anoop Sam John
>             Fix For: 2.0.0
>
>         Attachments: HBASE-15786.patch, HBASE-15786_V2.patch, 
> HBASE-15786_V2.patch, HBASE-15786_V3.patch, HBASE-15786_V4.patch, 
> HBASE-15786_V5.patch, HBASE-15786_V6.patch
>
>
> We can make use of MSLAB pool for this off heap memstore. 
> Right now one can specify the global memstore size (heap size) as a % of max 
> memory using a config. We will add another config with which one can specify 
> the global off heap memstore size. This will be exact size not as %. When off 
> heap memstore in use, we will give this entire area for the MSLAB pool and 
> that will create off heap chunks. So when cells are added to memstore, the 
> cell data gets copied into the off heap MSLAB chunk spaces. Note that when 
> the pool size is not really enough and we need additional chunk creation, we 
> wont use off heap area for that.  We dony want to create so many on demand 
> DBBs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to