You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Anoop Sam John (JIRA)" <ji...@apache.org> on 2017/02/14 10:13:41 UTC

[jira] [Updated] (HBASE-17338) Treat Cell data size under global memstore heap size only when that Cell can not be copied to MSLAB

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

Anoop Sam John updated HBASE-17338:
-----------------------------------
    Status: Open  (was: Patch Available)

> Treat Cell data size under global memstore heap size only when that Cell can not be copied to MSLAB
> ---------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-17338
>                 URL: https://issues.apache.org/jira/browse/HBASE-17338
>             Project: HBase
>          Issue Type: Sub-task
>          Components: regionserver
>    Affects Versions: 2.0.0
>            Reporter: Anoop Sam John
>            Assignee: Anoop Sam John
>             Fix For: 2.0.0
>
>         Attachments: HBASE-17338.patch, HBASE-17338_V2.patch, HBASE-17338_V2.patch
>
>
> We have only data size and heap overhead being tracked globally.  Off heap memstore works with off heap backed MSLAB pool.  But a cell, when added to memstore, not always getting copied to MSLAB.  Append/Increment ops doing an upsert, dont use MSLAB.  Also based on the Cell size, we sometimes avoid MSLAB copy.  But now we track these cell data size also under the global memstore data size which indicated off heap size in case of off heap memstore.  For global checks for flushes (against lower/upper watermark levels), we check this size against max off heap memstore size.  We do check heap overhead against global heap memstore size (Defaults to 40% of xmx)  But for such cells the data size also should be accounted under the heap overhead.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)