[ 
https://issues.apache.org/jira/browse/HBASE-29731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18042734#comment-18042734
 ] 

Hudson commented on HBASE-29731:
--------------------------------

Results for branch branch-2.6
        [build #392 on 
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/392/]:
 (x) *{color:red}-1 overall{color}*
----
details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/392/General_20Nightly_20Build_20Report/]


(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/392/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]


(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/392/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(x) {color:red}-1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/392/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 jdk17 hadoop3 checks{color}
-- For more information [see jdk17 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/392/JDK17_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 jdk17 hadoop 3.3.5 backward compatibility checks{color}
-- For more information [see jdk17 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/392/JDK17_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 jdk17 hadoop 3.3.6 backward compatibility checks{color}
-- For more information [see jdk17 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/392/JDK17_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 jdk17 hadoop 3.4.0 backward compatibility checks{color}
-- For more information [see jdk17 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/392/JDK17_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(x) {color:red}-1 jdk17 hadoop 3.4.1 backward compatibility checks{color}
-- For more information [see jdk17 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/392/JDK17_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


(/) {color:green}+1 client integration test for HBase 2 {color}
(/) {color:green}+1 client integration test for 3.3.5 {color}
(/) {color:green}+1 client integration test for 3.3.6 {color}
(/) {color:green}+1 client integration test for 3.4.0 {color}
(/) {color:green}+1 client integration test for 3.4.1 {color}
(/) {color:green}+1 client integration test for 3.4.2 {color}


> 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
>    Affects Versions: 3.0.0-beta-1, 2.7.0, 2.6.4
>            Reporter: Jaehui Lee
>            Assignee: Jaehui Lee
>            Priority: Trivial
>              Labels: pull-request-available
>             Fix For: 3.0.0, 2.7.0, 2.6.5
>
>
> 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)

Reply via email to