[
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.010.patch
1. Rewrite the description: "blockedFlushCount" -> "blockedFlushGauge", "un
blockedFlushCount" -> "unblockedFlushGauge"
2. Only update (un)blockedFlush histogram/gauge when (un)blockedFlushCount > 0
which means flushes did happen
3. tunerDoNothingCounter place in another else block, previous version was in
debug else block leading to unreachable in normal situation.
> 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, HBASE-14743.008.patch,
> HBASE-14743.009.patch, HBASE-14743.009.rw3.patch, HBASE-14743.009.v2.patch,
> HBASE-14743.010.patch, Metrics snapshot 2016-6-30.png, Screen Shot 2016-06-16
> at 5.39.13 PM.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)
