[ 
https://issues.apache.org/jira/browse/HBASE-24940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17190409#comment-17190409
 ] 

Hudson commented on HBASE-24940:
--------------------------------

Results for branch branch-2.3
        [build #28 on 
builds.a.o|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.3/28/]:
 (/) *{color:green}+1 overall{color}*
----
details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general 
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.3/28/General_20Nightly_20Build_20Report/]




(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) 
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.3/28/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]


(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.3/28/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11 
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.3/28/JDK11_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}


> runCatalogJanitor() API should return -1 to indicate already running status
> ---------------------------------------------------------------------------
>
>                 Key: HBASE-24940
>                 URL: https://issues.apache.org/jira/browse/HBASE-24940
>             Project: HBase
>          Issue Type: Improvement
>    Affects Versions: 2.2.3
>            Reporter: Mohammad Arshad
>            Assignee: Mohammad Arshad
>            Priority: Major
>             Fix For: 3.0.0-alpha-1, 1.7.0, 2.4.0, 2.3.2
>
>
> runCleanerChore() API returns false if hbck chore is already running. This is 
> quite helpful in many cases.
> runCatalogJanitor() API  is not indicating whether scan is already running. 
> Also it is not doing anything in case scan is already running.
> I think we should return -1 to indicate already running status.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to