Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BB4C410557 for ; Wed, 23 Apr 2014 04:51:25 +0000 (UTC) Received: (qmail 93536 invoked by uid 500); 23 Apr 2014 04:51:24 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 93479 invoked by uid 500); 23 Apr 2014 04:51:23 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 93447 invoked by uid 99); 23 Apr 2014 04:51:21 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Apr 2014 04:51:21 +0000 Date: Wed, 23 Apr 2014 04:51:21 +0000 (UTC) From: "Lars Hofhansl (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-3489) .oldlogs not being cleaned out MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-3489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13977828#comment-13977828 ] Lars Hofhansl commented on HBASE-3489: -------------------------------------- So is this still the case? That seems bad and wrong. > .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 was sent by Atlassian JIRA (v6.2#6252)