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

Posted to dev@hbase.apache.org by "Ted Yu (JIRA)" <ji...@apache.org> on 2015/06/27 03:45:05 UTC

[jira] [Created] (HBASE-13980) Distinguish blockedFlushCount vs unblockedFlushCount when tuning heap memory

Ted Yu created HBASE-13980:
------------------------------

             Summary: 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
            Priority: Minor


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)