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

Hudson commented on HBASE-20302:
--------------------------------

Results for branch branch-1.3
        [build #278 on 
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-1.3/278/]: 
(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/branch-1.3/278//General_Nightly_Build_Report/]


(x) {color:red}-1 jdk7 checks{color}
-- For more information [see jdk7 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-1.3/278//JDK7_Nightly_Build_Report/]


(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-1.3/278//JDK8_Nightly_Build_Report_(Hadoop2)/]




(/) {color:green}+1 source release artifact{color}
-- See build output for details.


> CatalogJanitor should log the reason why it is disabled
> -------------------------------------------------------
>
>                 Key: HBASE-20302
>                 URL: https://issues.apache.org/jira/browse/HBASE-20302
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Vishal Khandelwal
>            Assignee: Vishal Khandelwal
>            Priority: Major
>             Fix For: 1.5.0, 1.2.7, 1.3.3, 1.4.4
>
>         Attachments: HBASE-20302.branch-1.v1.patch
>
>
> when catalogJanitor is disabled it has various condition for which it can be 
> true to disable CatalogJanitor and sends this message "CatalogJanitor 
> disabled! Not running scan."  Since this is an async thread, it is difficult 
> to identify what is the exact reason for it disable. We could log all 
> conditions alongwith  LOG.warn("CatalogJanitor disabled! Not running scan.") 
> for better debugging.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to