[
https://issues.apache.org/jira/browse/HBASE-18652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16163345#comment-16163345
]
Biju Nair commented on HBASE-18652:
-----------------------------------
Thanks @stack for the review.
bq. how often are we calling the getL1? Everytime we want to update counters or
just at startup?
Only on startup. BTW in {{master}} this is already defined {{synchronized}}
bq. Would subtracting L1 hits from global hits work for L2 hit count?
>From the UI we can get a point in time values. By exposing these already
>available cache stats through JMX helps users understand the usage pattern by
>storing them.
> Expose individual cache stats in a CombinedCache through JMX
> ------------------------------------------------------------
>
> Key: HBASE-18652
> URL: https://issues.apache.org/jira/browse/HBASE-18652
> Project: HBase
> Issue Type: Improvement
> Components: regionserver
> Reporter: Biju Nair
> Assignee: Biju Nair
> Fix For: 1.4.0, 1.5.0, 2.0.0-alpha-3
>
> Attachments: 18652-branch-1-V3.0.PATCH, HBASE-18652-addendum.patch,
> HBASE-18652-BRANCH-1.PATCH, HBASE-18652-branch-1-v1.0.patch,
> HBASE-18652-branch-1-V2.0.PATCH, HBASE-18652-branch-1-V3.0.PATCH,
> HBASE-18652.PATCH, HBASE-18652-V1.0.PATCH, HBASE-18652-V2.0.PATCH,
> HBASE-18652-WIP.PATCH
>
>
> With offHeap cache being used to store data blocks and on-heap for index and
> bloom filters, exposing the stats from the individual caches through JMX will
> help understand the cache usage trend. Currently the combined cache stats is
> available through JMX which may not provide insight into the individual cache
> usage.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
