[
https://issues.apache.org/jira/browse/HBASE-24361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17113150#comment-17113150
]
Hudson commented on HBASE-24361:
--------------------------------
Results for branch master
[build #1733 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/1733/]: (x)
*{color:red}-1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1733/General_20Nightly_20Build_20Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1663//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1733/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1733/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(x) {color:red}-1 client integration test{color}
--Failed when running client tests on top of Hadoop 3. [see log for
details|https://builds.apache.org/job/HBase%20Nightly/job/master/1733//artifact/output-integration/hadoop-3.log].
(note that this means we didn't check the Hadoop 3 shaded client)
> Make `RESTApiClusterManager` more resilient
> -------------------------------------------
>
> Key: HBASE-24361
> URL: https://issues.apache.org/jira/browse/HBASE-24361
> Project: HBase
> Issue Type: Test
> Components: integration tests
> Affects Versions: 2.3.0
> Reporter: Nick Dimiduk
> Assignee: Nick Dimiduk
> Priority: Major
> Fix For: 3.0.0-alpha-1, 2.3.0
>
>
> The Cloudera Manager API client in {{RESTApiClusterManager}} appears to
> assume that API calls sent to CM for process commands block on command
> completion. However, these commands are "asynchronous," queuing work in the
> background for execution. Update the client to track command submission and
> block on completion of that commandId. This allows this {{ClusterManager}} to
> conform to the expectations of the {{Actions}} that invoke it.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
