hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] Created: (HBASE-834) Upper bound on files we compact at any one time
Date Fri, 15 Aug 2008 23:39:44 GMT
Upper bound on files we compact at any one time

                 Key: HBASE-834
                 URL: https://issues.apache.org/jira/browse/HBASE-834
             Project: Hadoop HBase
          Issue Type: Improvement
            Reporter: stack
            Priority: Minor

>From Billy in HBASE-64, which we closed because it got pulled all over the place:

Currently we do compaction on a region when the hbase.hstore.compactionThreshold is reached
- default 3

I thank we should configure a max number of mapfiles to compact at one time simulator to doing
a minor compaction in bigtable. This keep compaction's form getting tied up in one region
to long letting other regions get way to many memcache flushes making compaction take longer
and longer for each region

If we did that when a regions updates start to slack off the max number will eventuly include
all mapfiles causeing a major compaction on that region. Unlike big table this would leave
the master out of the process and letting the region server handle the major compaction when
it has time.

When doing a minor compaction on a few files I thank we should compact the newest mapfiles
first leave the larger/older ones for when we have low updates to a region.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message