[
https://issues.apache.org/jira/browse/HBASE-28876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17889413#comment-17889413
]
Hudson commented on HBASE-28876:
--------------------------------
Results for branch master
[build #1183 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/1183/]:
(/) *{color:green}+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/master/1183/General_20Nightly_20Build_20Report/]
(/) {color:green}+1 jdk17 hadoop3 checks{color}
-- For more information [see jdk17
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/1183/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{color}
> Should call ProcedureSchduler.completionCleanup for non-root procedure too
> --------------------------------------------------------------------------
>
> Key: HBASE-28876
> URL: https://issues.apache.org/jira/browse/HBASE-28876
> Project: HBase
> Issue Type: Bug
> Components: proc-v2
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.0, 3.0.0-beta-2, 2.6.1, 2.5.11
>
>
> Per the discussion in this PR
> https://github.com/apache/hbase/pull/6247
> And the related issue HBASE-28830, it seems incorrect that we only call
> cleanup for non-root procedures.
> This issue aims to see if there are any issues we call this method for every
> procedure.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
