Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Date: Mon, 19 Dec 2016 13:18:58 +0000 (UTC)
From: "Anoop Sam John (JIRA)" <jira@apache.org>
To: dev@hbase.apache.org
Message-ID: <JIRA.13029131.1482153529000.553026.1482153538423@Atlassian.JIRA>
In-Reply-To: <JIRA.13029131.1482153529000@Atlassian.JIRA>
References: <JIRA.13029131.1482153529000@Atlassian.JIRA> <JIRA.13029131.1482153529589@arcas>
Subject: [jira] [Created] (HBASE-17338) Treat Cell data size under global
 memstore heap size only when that Cell can not be copied to MSLAB
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 19 Dec 2016 13:19:00 -0000

Anoop Sam John created HBASE-17338:
--------------------------------------

             Summary: 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
    Affects Versions: 2.0.0
            Reporter: Anoop Sam John
            Assignee: Anoop Sam John
             Fix For: 2.0.0


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.4#6332)