[ https://issues.apache.org/jira/browse/HBASE-23283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16975013#comment-16975013 ]
Hudson commented on HBASE-23283: -------------------------------- Results for branch branch-1 [build #1138 on builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-1/1138/]: (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/1138//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/1138//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/1138//JDK8_Nightly_Build_Report_(Hadoop2)/] (/) {color:green}+1 source release artifact{color} -- See build output for details. > Provide clear and consistent logging about the period of enabled chores > ----------------------------------------------------------------------- > > Key: HBASE-23283 > URL: https://issues.apache.org/jira/browse/HBASE-23283 > Project: HBase > Issue Type: Improvement > Components: Operability > Affects Versions: 3.0.0, 2.3.0, 1.7.0 > Reporter: Sean Busbey > Assignee: Mingliang Liu > Priority: Minor > Fix For: 3.0.0, 2.3.0, 1.6.0, 2.1.8, 2.2.3 > > Attachments: HBASE-23283.000.patch > > > Similar to HBASE-23038, we should always log info about our enabled chores. > Right now wether or not we get some information is up to particular Chore > constructors and by and large we don't get any log messages when things can > get started, even if the period is something impossibly long (e.g. 3000 days). > When we go to schedule the chore here: > {code} > if (chore.getPeriod() <= 0) { > LOG.info("The period is {} seconds, {} is disabled", > chore.getPeriod(), chore.getName()); > return false; > } > {code} > we should add an else clause that says it's enabled. It looks like we could > then just call chore.toString to get the proper details about the chore and > its period. -- This message was sent by Atlassian Jira (v8.3.4#803005)