You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Dave Latham (JIRA)" <ji...@apache.org> on 2013/02/26 22:22:14 UTC

[jira] [Commented] (HBASE-3489) .oldlogs not being cleaned out

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

Dave Latham commented on HBASE-3489:
------------------------------------

The ReplicationLogCleaner prevents any oldlogs from being cleaned if replication is enabled in the config (hbase-site.xml) but stopped (via stop_replication).  That caused this issue for us, and my guess is it might be behind other people's cases too.
                
> .oldlogs not being cleaned out
> ------------------------------
>
>                 Key: HBASE-3489
>                 URL: https://issues.apache.org/jira/browse/HBASE-3489
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 0.90.0
>         Environment: 10 Nodes Write Heavy Cluster
>            Reporter: Wayne
>         Attachments: oldlog.txt
>
>
> The .oldlogs folder is never being cleaned up. The hbase.master.logcleaner.ttl has been set to clean up the old logs but the clean up is never kicking in. The limit of 10 files is not the problem. After running for 5 days not a single log file has ever been deleted and the logcleaner is set to 2 days (from the default of 7 days). It is assumed that the replication changes that want to be sure to keep these logs around if needed have caused the cleanup to be blocked. There is no replication defined (knowingly).
>  

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira