hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Reid Chan (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-14743) Add metrics around HeapMemoryManager
Date Sat, 11 Jun 2016 14:47:21 GMT

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

Reid Chan updated HBASE-14743:
    Attachment: HBASE-14743.008.patch

"How many decided to expand memstore" √
"How many decided to expand block cache" √
"How many decided to do nothing" √
How many times that the heap occupancy is above the low watermark.

This patch improves the documentation according to reviews, removes duplicated metrics.
It Also provides histograms for those factors that have impact on the tuner result: cacheEvictedCount,
cacheMissCount, blockedFlushCount, unblockedFlushCount, curMemStoreUsed and curBlockCacheUsed.
In particular, the histograms for curMemStoreUsed and curBlockCacheUsed are shown in two aspects.
One is in size which is more straightforward, the other is in percentage which is more statistical.


> Add metrics around HeapMemoryManager
> ------------------------------------
>                 Key: HBASE-14743
>                 URL: https://issues.apache.org/jira/browse/HBASE-14743
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Elliott Clark
>            Assignee: Reid Chan
>            Priority: Minor
>         Attachments: HBASE-14743.001.patch, HBASE-14743.002.patch, HBASE-14743.003.patch,
HBASE-14743.004.patch, HBASE-14743.005.patch, HBASE-14743.006.patch, HBASE-14743.007.patch,
> it would be good to know how many invocations there have been.
> How many decided to expand memstore.
> How many decided to expand block cache.
> How many decided to do nothing.
> etc.
> When that's done use those metrics to clean up the tests.

This message was sent by Atlassian JIRA

View raw message