[
https://issues.apache.org/jira/browse/HBASE-29232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17943978#comment-17943978
]
Hudson commented on HBASE-29232:
--------------------------------
Results for branch branch-3
[build #404 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3/404/]:
(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-3/404/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/branch-3/404/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-3/404/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-3/404/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-3/404/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}
> give up retrying earlier for some admin operations
> --------------------------------------------------
>
> Key: HBASE-29232
> URL: https://issues.apache.org/jira/browse/HBASE-29232
> Project: HBase
> Issue Type: Improvement
> Components: asyncclient, Client
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Major
> Labels: pull-request-available
> Fix For: 3.0.0-beta-2
>
>
> WHen running ITBLL, I found that if the region is moved during some actions,
> the operation will retry forever.
> The problem is that, when constructing AsyncAdminRequestRetryingCaller, we
> will pass the server name in. This is not a problem when we do some region
> server specific operations, like get metrics from region server, but for
> region operations, since it could be moved, retrying on the same region
> server does not help.
> At least we should fail the request without retrying until reaching the limit
> when hitting NotServingRegionException, or we should implement region
> relocating logic here.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
