[
https://issues.apache.org/jira/browse/HBASE-14743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15335688#comment-15335688
]
Reid Chan commented on HBASE-14743:
-----------------------------------
I think the memory tuner in the memory manager didn't turn on which leads to
all zero.
To turn on the tuner, we need to add some configurations to meet the
requirements.
a) "hbase.regionserver.global.memstore.size.max.range" and
"hbase.regionserver.global.memstore.size.min.range". If not set, each of their
value is equal to the value of "hbase.regionserver.global.memstore.size" or
"hbase.regionserver.global.memstore.upperLimit" (both are 0.4 by default). The
first requirement is that memstore min max range can't be the same.
b) "hfile.block.cache.size.max.range" and "hfile.block.cache.size.min.range".
If not set, each of their value is equal to "hfile.block.cache.size" which is
0.4 by default. The second requirement is that blockcache min max range can't
be the same.
c) I will just write the configuration name in short. The Third requirement is
the sum of (memstore.size.min.range + blockcache.max.range +
L2BlockCachePercent <= 0.8) and the sum of (memstore.max.range +
blockcache.min.range + L2BlockCachePercent <= 0.8).
Only all the requirements meet will me see the memory metrics work. Hope that I
have stated it clearly, if not, i will recommend to take a look at the private
method "doInit" in the HeapMemoryManager.java. I think code is better than my
words.
Ps, there are some problems in the third requirement, but they are not the
problems that this issue cares about. I may state it in another issue.
> 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,
> 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)
