You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Bryan Beaudreault (Jira)" <ji...@apache.org> on 2022/07/10 12:40:00 UTC

[jira] [Assigned] (HBASE-27186) Report block cache size metrics separately for L1 and L2

     [ https://issues.apache.org/jira/browse/HBASE-27186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bryan Beaudreault reassigned HBASE-27186:
-----------------------------------------

    Assignee: Bryan Beaudreault

> Report block cache size metrics separately for L1 and L2
> --------------------------------------------------------
>
>                 Key: HBASE-27186
>                 URL: https://issues.apache.org/jira/browse/HBASE-27186
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Bryan Beaudreault
>            Assignee: Bryan Beaudreault
>            Priority: Minor
>
> Currently, in terms of block cache size metrics, we report the following: blockCacheFreeSize, blockCacheCount, blockCacheSize, blockCacheEvictionCount. This isn't super useful when running with BucketCache, because in that case L1 (holding index/meta blocks) and L2 (holding data blocks) operate largely independently. Additionally, you might typically report on block cache sizes in terms of monitoring heap usage. But with BucketCache, the cache is off-heap, so it becomes a misleading metric in that case.
> We have metrics l1CacheHitCount/MissCount/HitRatio/MissRatio, and the same for l2. We should add l1CacheFreeSize, l1CacheSize, l1CacheCount, l1CacheEvictionCount, and the same for l2.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)