You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2025/11/26 04:07:00 UTC
[jira] [Updated] (HBASE-29731) Add L1 and L2 cache hit/miss caching metrics
[ https://issues.apache.org/jira/browse/HBASE-29731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated HBASE-29731:
-----------------------------------
Labels: pull-request-available (was: )
> Add L1 and L2 cache hit/miss caching metrics
> --------------------------------------------
>
> Key: HBASE-29731
> URL: https://issues.apache.org/jira/browse/HBASE-29731
> Project: HBase
> Issue Type: Improvement
> Components: BlockCache
> Reporter: Jaehui Lee
> Assignee: Jaehui Lee
> Priority: Minor
> Labels: pull-request-available
>
> h2. Description
> Currently, HBase provides hit/miss caching metrics only at the overall BlockCache level. While the general hit ratio includes all read operations, we prefer using the hit caching ratio because it excludes non-cached reads (such as those from compactions) that would otherwise skew the overall hit ratio downward.
> When using only L1 cache, the existing BlockCache-level metrics are sufficient. However, when both L1 and L2 caches are enabled, CompoundBlockCache reports aggregated metrics (L1 + L2 combined), making it impossible to monitor the hit/miss caching ratio for each cache tier individually.
> h2. Proposed Solution
> Add separate hit/miss caching metrics for L1 and L2 caches to enable independent monitoring of each cache tier's performance.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)