[
https://issues.apache.org/jira/browse/HADOOP-2615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12562361#action_12562361
]
stack commented on HADOOP-2615:
-------------------------------
Here's the next two compactions:
{code}
2008-01-25 01:58:30,280 INFO org.apache.hadoop.hbase.HRegion: compaction
completed on region TestTable,,1201223677355. Took 20mins, 34sec
2008-01-25 02:17:28,818 INFO org.apache.hadoop.hbase.HRegion: compaction
completed on region TestTable,,1201223677355. Took 18mins, 58sec
{code}
The split final runs, 15 minutes after the loading finishes and an hour after
its initially scheduled. Split is frozen out waiting here in HRegion:
{code}
while (writestate.compacting || writestate.flushing) {
LOG.debug("waiting for" +
(writestate.compacting ? " compaction" : "") +
(writestate.flushing ?
(writestate.compacting ? "," : "") + " cache flush" :
""
) + " to complete for region " + regionName
);
try {
writestate.wait();
} catch (InterruptedException iex) {
// continue
}
}
{code}
> Add max number of mapfiles to compact at one time giveing us a minor & major
> compaction
> ---------------------------------------------------------------------------------------
>
> Key: HADOOP-2615
> URL: https://issues.apache.org/jira/browse/HADOOP-2615
> Project: Hadoop Core
> Issue Type: Improvement
> Components: contrib/hbase
> Reporter: Billy Pearson
> Priority: Minor
> Fix For: 0.17.0
>
>
> 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.
