[
https://issues.apache.org/jira/browse/HBASE-29714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18039006#comment-18039006
]
Hudson commented on HBASE-29714:
--------------------------------
Results for branch master
[build #1372 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/1372/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(x) {color:red}-1 general checks{color}
-- For more information [see general
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/1372/General_20Nightly_20Build_20Report/]
(x) {color:red}-1 jdk17 hadoop3 checks{color}
-- For more information [see jdk17
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/1372/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/master/1372/JDK17_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(x) {color:red}-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/master/1372/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 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}
> Increase DEFAULT_RS_REMOTE_PROC_RETRY_LIMIT to 10
> -------------------------------------------------
>
> Key: HBASE-29714
> URL: https://issues.apache.org/jira/browse/HBASE-29714
> Project: HBase
> Issue Type: Improvement
> Components: proc-v2
> Reporter: Umesh Kumar Kumawat
> Assignee: Umesh Kumar Kumawat
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.0, 3.0.0-beta-2, 2.6.5
>
>
> DEFAULT_RS_RPC_RETRY_INTERVAL is 100 second and
> DEFAULT_RS_REMOTE_PROC_RETRY_LIMIT is 5 so we are aborting the RS in just 3
> seconds
> 2025-11-07 11:48:36,298 WARN [RSProcedureDispatcher-pool-30146]
> procedure.RSProcedureDispatcher - request to rs1,xxx,1762426870165 failed due
> to org.apache.hadoop.hbase.exceptions.ConnectionClosedException: Call to
> address=rs1:xxx failed on local exception:
> org.apache.hadoop.hbase.exceptions.ConnectionClosedException: Connection
> closed, try=0, retrying...
>
> 2025-11-07 11:48:36,399 WARN [RSProcedureDispatcher-pool-30136]
> procedure.RSProcedureDispatcher - request to rs1,xxx,1762426870165 failed due
> to java.io.IOException: Call to address=rs1:xxx failed on local exception:
> java.io.IOException: Can not send request because relogin is in progress.,
> try=1, retrying... ,
> 2025-11-07 11:48:36,799 WARN [RSProcedureDispatcher-pool-30116]
> procedure.RSProcedureDispatcher - request to rs1,xxx,1762426870165 failed due
> to java.io.IOException: Call to address=rs1:xxx failed on local exception:
> java.io.IOException: Can not send request because relogin is in progress.,
> try=2, retrying...
> 2025-11-07 11:48:37,700 WARN [RSProcedureDispatcher-pool-30088]
> procedure.RSProcedureDispatcher - request to rs1,xxx,1762426870165 failed due
> to java.io.IOException: Call to address=rs1:xxx failed on local exception:
> java.io.IOException: Can not send request because relogin is in progress.,
> try=3, retrying...
> 2025-11-07 11:48:39,301 WARN [RSProcedureDispatcher-pool-30124]
> procedure.RSProcedureDispatcher - Number of retries 5 exceeded limit 5 for
> the given error type. Scheduling server crash for rs1,xxx,1762426870165
>
> as per the logs in just 100(1^2+2^2+3^2+4^2) seconds RS got aborted. Taking
> hte example of RITThreshold as 60 seconds, we should at least wait for 30
> seconds. that will happen if we wait keep the
> DEFAULT_RS_REMOTE_PROC_RETRY_LIMIT 10 (28.5 seconds).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
