[
https://issues.apache.org/jira/browse/HBASE-29280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17952534#comment-17952534
]
Hudson commented on HBASE-29280:
--------------------------------
Results for branch branch-2.6
[build #315 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/315/]:
(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/315/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/315/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/315/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/315/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/315/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/315/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/315/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/315/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/315//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/315//console].
> Bug in RawAsyncTableImpl#coprocessorServiceUntilComplete retry logic
> --------------------------------------------------------------------
>
> Key: HBASE-29280
> URL: https://issues.apache.org/jira/browse/HBASE-29280
> Project: HBase
> Issue Type: Bug
> Reporter: Charles Connell
> Assignee: Charles Connell
> Priority: Minor
> Labels: pull-request-available
> Fix For: 2.7.0, 3.0.0-beta-2, 2.6.3
>
>
> I noticed a bug that I introduced in HBASE-28770. I introduced the ability
> for coprocessor endpoints to send partial responses. When this happens, the
> client needs to send a new request to fetch remaining results, and may sleep
> before doing so. The logic for sleeping looks like:
> {code:java}
> if (waitInterval.isZero()) {
> AsyncConnectionImpl.RETRY_TIMER.newTimeout(
> (timeout) -> coprocessorServiceUntilComplete(stubMaker, updatedCallable,
> callback,
> locateFinished, unfinishedRequest, region, span),
> waitInterval.toMillis(), TimeUnit.MILLISECONDS);
> } else {
> coprocessorServiceUntilComplete(stubMaker, updatedCallable, callback,
> locateFinished,
> unfinishedRequest, region, span);
> } {code}
> which has backwards logic. The first line should read
> {code:java}
> if (!waitInterval.isZero()) {}
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
