You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Hudson (Jira)" <ji...@apache.org> on 2024/12/20 04:27:00 UTC
[jira] [Commented] (HBASE-29035) Amount of region cached in the region metrics not updated for a region immediately after it is flushed with cacheOnWrite turned on
[ https://issues.apache.org/jira/browse/HBASE-29035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17907273#comment-17907273 ]
Hudson commented on HBASE-29035:
--------------------------------
Results for branch branch-2
[build #1206 on builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/1206/]: (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/1206/General_20Nightly_20Build_20Report/]
(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/1206/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/1206/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(x) {color:red}-1 jdk17 hadoop3 checks{color}
-- For more information [see jdk17 report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/1206/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}
> Amount of region cached in the region metrics not updated for a region immediately after it is flushed with cacheOnWrite turned on
> ----------------------------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-29035
> URL: https://issues.apache.org/jira/browse/HBASE-29035
> Project: HBase
> Issue Type: Bug
> Components: Balancer, BucketCache
> Affects Versions: 3.0.0-beta-1, 4.0.0-alpha-1, 2.7.0, 2.6.1
> Reporter: Rahul Agarkar
> Assignee: Rahul Agarkar
> Priority: Major
> Labels: pull-request-available
> Fix For: 3.0.0, 4.0.0-alpha-1, 2.7.0
>
>
> An issue has been observed where if a new region is created and flushed with the configuration "hbase.rs.cacheblocksonwrite" is set to true, then, the region metrics does not reflect the amount of region cached for this new region. It starts reflecting the correct metric when this region is reopened for whatever reason.
>
> The steps to reproduce this issue are as follows:
> * Create a table {{create 'tprefetch', 'cf'}}
> * {{{}{}}}Insert a record in the table {{put 'tprefetch', 'row1', 'cf:col1', 'aaaaa'}}
> * {{{}{}}}{{{}flush 'tprefetch'{}}}
> After the flush, query the region metrics for this region and it will show that the region is 05 cached. This leads to the cacheAwareLoadBalancer take incorrect decisions whenever a region server is restarted.
> {{}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)