[
https://issues.apache.org/jira/browse/HBASE-14743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Reid Chan updated HBASE-14743:
------------------------------
Release Note:
A memory metrics reveals situations happened in both MemStores and BlockCache
in RegionServer. Through this metrics, users/operators can know
1). Current size of MemStores and BlockCache in bytes.
2). Occurrence for Memstore minor and major flush. (named unblocked flush and
blocked flush respectively, shown in histogram)
3). Dynamic changes in size between MemStores and BlockCache. (with
Increase/Decrease as prefix, shown in histogram). And a counter for no changes,
named DoNothingCounter.
4). Occurrence for memory usage alarm (used more than 95% by default) in
RegionServer. (named AboveHeapOccupancyLowWatermarkCounter)
was:A Memory metrics for RegionServer. It reveals situations happened in both
MemStore and BlockCache.
> 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
> Fix For: 2.0.0
>
> Attachments: HBASE-14743.009.patch, HBASE-14743.009.rw3.patch,
> HBASE-14743.009.v2.patch, HBASE-14743.010.patch, HBASE-14743.010.v2.patch,
> HBASE-14743.011.patch, Metrics snapshot 2016-6-30.png, Screen Shot 2016-06-16
> at 5.39.13 PM.png, test2_1.png, test2_2.png, test2_3.png, test2_4.png
>
>
> 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
(v6.3.4#6332)
