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

Hudson commented on HBASE-20554:
--------------------------------

Results for branch branch-1.4
        [build #316 on 
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-1.4/316/]: 
(x) *{color:red}-1 overall{color}*
----
details (if available):

(x) {color:red}-1 general checks{color}
-- For more information [see general 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-1.4/316//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.4/316//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.4/316//JDK8_Nightly_Build_Report_(Hadoop2)/]




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


> "WALs outstanding" message from CleanerChore is noisy
> -----------------------------------------------------
>
>                 Key: HBASE-20554
>                 URL: https://issues.apache.org/jira/browse/HBASE-20554
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Andrew Purtell
>            Assignee: Andrew Purtell
>            Priority: Trivial
>             Fix For: 3.0.0, 2.1.0, 1.5.0, 2.0.1, 1.4.5
>
>         Attachments: HBASE-20554.patch
>
>
> WARN level "WALs outstanding" from CleanerChore should be DEBUG and are not 
> always correct. 
> I left a cluster configured for ITBLL (retaining all WALs for post hoc 
> analysis) and in the morning found the master log full of "WALs outstanding" 
> warnings from CleanerChore. 
> Should this really be a warning?
> {quote}
> 2018-05-09 16:42:03,893 WARN  
> [node-1.cluster,16000,1525851521469_ChoreService_2] cleaner.CleanerChore: 
> WALs outstanding under hdfs://node-1.cluster/hbase/oldWALs
> {quote}
> If someone has configured really long WAL retention then having WALs in 
> oldWALs will be normal. 
> Also, it seems the warning is sometimes incorrect.
> {quote}
> 2018-05-09 16:42:24,751 WARN  
> [node-1.cluster,16000,1525851521469_ChoreService_1] cleaner.CleanerChore: 
> WALs outstanding under hdfs://node-1.cluster/hbase/archive
> {quote}
> There are no WALs under archive/. 
> Even at DEBUG level, if it is not correct, then it can lead an operator to be 
> concerned about nothing, so better to just remove it.



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

Reply via email to