[
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.v2.patch
can't pass the tests in the TestHeapMemoryManager because of the default value
of the min/max range. i remove them in the patch 011, and just keep them as
origin.
the metrics by default will be off and show zero in the MBeans, improve it in
the feature as suggestion. sorry for my stubborn.
> 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, 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)
