[
https://issues.apache.org/jira/browse/HBASE-30102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18077656#comment-18077656
]
Hudson commented on HBASE-30102:
--------------------------------
Results for branch master
[build #56 on
builds.a.o|https://ci-hbase.apache.org/job/HBase-Integration-Test/job/master/56/]:
(/) *{color:green}+1 overall{color}*
----
details (if available):
(/) {color:green}+1 client integration test for 3.3.5 {color}
(/) {color:green}+1 client integration test for 3.3.5 with shaded hadoop
client{color}
(/) {color:green}+1 client integration test for 3.3.6 {color}
(/) {color:green}+1 client integration test for 3.3.6 with shaded hadoop
client{color}
(/) {color:green}+1 client integration test for 3.4.0 {color}
(/) {color:green}+1 client integration test for 3.4.0 with shaded hadoop
client{color}
(/) {color:green}+1 client integration test for 3.4.1 {color}
(/) {color:green}+1 client integration test for 3.4.1 with shaded hadoop
client{color}
(/) {color:green}+1 client integration test for 3.4.2 {color}
(/) {color:green}+1 client integration test for 3.4.2 with shaded hadoop
client{color}
(/) {color:green}+1 client integration test for 3.4.3 {color}
(/) {color:green}+1 client integration test for 3.4.3 with shaded hadoop
client{color}
> Add metric to account for region data classified as cold by the Time Based
> Priority logic
> -----------------------------------------------------------------------------------------
>
> Key: HBASE-30102
> URL: https://issues.apache.org/jira/browse/HBASE-30102
> Project: HBase
> Issue Type: Sub-task
> Affects Versions: 3.0.0-beta-1, 2.6.5
> Reporter: Wellington Chevreuil
> Assignee: Wellington Chevreuil
> Priority: Major
> Labels: pull-request-available
> Fix For: 3.0.0, 2.7.0, 2.6.6
>
> Attachments: Screenshot 2026-04-24 at 12.52.43.png
>
>
> This is to account and report total size of region data identified as cold by
> the Time Based Priority logic in the region metrics. We should also expose it
> in the RS UI, as we do have a "% Cached" field, it would help distinguish
> when a low cache ratio is legit (due to time based priority), from when it's
> indeed a caching management problem.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
