[
https://issues.apache.org/jira/browse/HBASE-29180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17937548#comment-17937548
]
Hudson commented on HBASE-29180:
--------------------------------
Results for branch branch-2.5
[build #673 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.5/673/]:
(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.5/673/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.5/673/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.5/673/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.5/673/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.5/673/JDK17_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk17 hadoop 3.2.4 backward compatibility checks{color}
-- For more information [see jdk17
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.5/673/JDK17_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(x) {color:red}-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.5/673/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.5/673//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.5/673//console].
> Apply fail-fast retry limit for UnknownHostException
> ----------------------------------------------------
>
> Key: HBASE-29180
> URL: https://issues.apache.org/jira/browse/HBASE-29180
> Project: HBase
> Issue Type: Sub-task
> Affects Versions: 2.5.11
> Reporter: Viraj Jasani
> Assignee: Viraj Jasani
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.0, 3.0.0-beta-2, 2.6.3, 2.5.12
>
>
> As part of HBASE-28638, fail-fast retry limit has been introduced for errors
> like CallQueueTooBigException, SaslException, ConnectionClosedException. This
> helps limit the num of retries that RSProcedureDispatcher has to perform
> while executing remote procedures. Since the region open/close fails on the
> remote server, we also trigger SCP for the target server.
> We recently came across UnknownHostException as another example of where the
> remote calls can get stuck forever:
> {code:java}
> WARN [RSProcedureDispatcher-pool-98034] procedure.RSProcedureDispatcher -
> request to rs1.xyz,60020,1739254267238 failed due to
> java.net.UnknownHostException: Call to address=rs1.xyz:60020 failed on local
> exception: java.net.UnknownHostException: rs1.xyz:60020 could not be
> resolved, try=2867, retrying... , request params: open_region {
> open_info {
> region {
> ...
> ... {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
