Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hbase.apache.org
Received-SPF: pass (athena.apache.org: domain of saint.ack@gmail.com
 designates 209.85.215.41 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:sender:in-reply-to:references:date
         :x-google-sender-auth:message-id:subject:from:to:content-type;
        b=c6Vkf9bIJ+S4yKzZc24S61FXNFKoBdv1O7RbGxI2YMWJN1pXASko9Jy8yyrYAycd/C
         wvuXDituOX2nebTdKSUo+GiPpSkXTQW4IGmmV6+rz5jFwK7v2Ok+7Nxq9v5eNFT5yCIq
         ICFVTqsMJLUw+JJYm9FTzZyF8H32LUzz0hLbg=
MIME-Version: 1.0
Sender: saint.ack@gmail.com
In-Reply-To: <AANLkTikpM0u918wO3o-v8APVqCE6M1SPFLcjW+mze51J@mail.gmail.com>
References: <AANLkTikpM0u918wO3o-v8APVqCE6M1SPFLcjW+mze51J@mail.gmail.com>
Date: Fri, 28 Jan 2011 09:56:06 -0800
Message-ID: <AANLkTi=_8+XW0bg3iod=EpNmOP0jK_=fWPPGWyO4g5Oy@mail.gmail.com>
Subject: Re: .oldlogs Cleanup
From: Stack <stack@duboce.net>
To: user@hbase.apache.org
Content-Type: text/plain; charset=ISO-8859-1

There is http://hbase.apache.org/configuration.html#hbase.master.logcleaner.ttl
and 'this.maxLogs = conf.getInt("hbase.regionserver.maxlogs", 32);'
(The latter does not seem to be hbase-default.xml which looks like a
bit of an oversight.

Check a few of the older ones.  See if you can figure if they are
still in use on the regionserver whose directory they are in.    Make
sure they are > an hour old.  There might be a bug in our cleanup code
(It changed in 0.90.0 to acoomodate replication and others who want to
be up on state of WAL).

St.Ack

On Fri, Jan 28, 2011 at 9:40 AM, Wayne <wav100@gmail.com> wrote:
> How is the .oldlogs folder cleaned up? My cluster size kept going up and I
> looked closely and realized that 91% of the space was going to .oldlogs that
> do not appear to be archived. This adds up to 12.5TB with rf=3 in the 4 days
> we have been up with .90. How can this be configured to be cleaned out more
> regularly?
>
> Thanks.
>