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

Hudson commented on HBASE-29245:
--------------------------------

Results for branch branch-2.6
        [build #327 on 
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/327/]:
 (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/327/General_20Nightly_20Build_20Report/]


(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/327/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/327/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/327/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/327/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/327/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/327/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/327/JDK17_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(x) {color:red}-1 source release artifact{color}
-- Something went wrong with this stage, [check relevant console 
output|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/327//console].


(x) {color:red}-1 client integration test{color}
-- Something went wrong with this stage, [check relevant console 
output|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/327//console].


> Region reopening batch size not increased when backoff is zero
> --------------------------------------------------------------
>
>                 Key: HBASE-29245
>                 URL: https://issues.apache.org/jira/browse/HBASE-29245
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Junegunn Choi
>            Assignee: Junegunn Choi
>            Priority: Minor
>              Labels: pull-request-available
>             Fix For: 2.7.0, 3.0.0-beta-2, 2.6.3
>
>         Attachments: image-2025-04-08-15-46-35-759.png, 
> image-2025-04-08-15-46-44-588.png
>
>
> h2. Problem
> {{hbase.reopen.table.regions.progressive.batch.size.max}} added in 
> HBASE-28215 is for making HBase reopen regions in batches on an alter 
> operation. The batch size is expected to be gradually increased from 1 to the 
> specified maximum. (i.e. 1, 2, 4, 8, 16, ..., max) However, when 
> {{hbase.reopen.table.regions.progressive.batch.backoff.ms}} is set to 0, 
> which is the default, the batch size is not increased. So whatever the 
> maximum value is, HBase will reopen only one region at a time.
> h2. Workaround
> Use a non-zero backoff value, such as 1, even if you don't need backoff.
> h2. Solution
> Make a slight modification to the code so that the batch size is increased 
> even when backoff is 0.
> h2. Test
> The existing test case was updated to validate the progressive growth of the 
> batch size.
> h2. Manual testing
> Tested the fix locally, and confirmed that the batch size increases as 
> expected.
>  !image-2025-04-08-15-46-35-759.png|width=600! 
>  !image-2025-04-08-15-46-44-588.png|width=600! 



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

Reply via email to