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 <[email protected]> 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. >
