Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 30 Jun 2015 04:31:04 +0000 (UTC)
From: "Abhilash (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12841042.1435369481000.54264.1435638664704@Atlassian.JIRA>
In-Reply-To: <JIRA.12841042.1435369481000@Atlassian.JIRA>
References: <JIRA.12841042.1435369481000@Atlassian.JIRA>
 <JIRA.12841042.1435369481702@arcas>
Subject: [jira] [Updated] (HBASE-13980) Distinguish blockedFlushCount vs
 unblockedFlushCount when tuning heap memory
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Abhilash updated HBASE-13980:
-----------------------------
    Attachment: HBASE-13980.patch

> Distinguish blockedFlushCount vs unblockedFlushCount when tuning heap memory
> ----------------------------------------------------------------------------
>
>                 Key: HBASE-13980
>                 URL: https://issues.apache.org/jira/browse/HBASE-13980
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Ted Yu
>            Assignee: Abhilash
>            Priority: Minor
>         Attachments: HBASE-13980.patch
>
>
> Currently DefaultHeapMemoryTuner doesn't distinguish blockedFlushCount vs unblockedFlushCount.
> In its tune() method:
> {code}
>     long totalFlushCount = blockedFlushCount+unblockedFlushCount;
>     rollingStatsForCacheMisses.insertDataValue(cacheMissCount);
>     rollingStatsForFlushes.insertDataValue(totalFlushCount);
> {code}
> Occurrence of blocked flush indicates that upper limit for memstore is not sufficient.
> We should either give blockedFlushCount more weight or, take tuning action based on blockedFlushCount directly.
> See discussion from tail of HBASE-13876.


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