[
https://issues.apache.org/jira/browse/HBASE-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12622323#action_12622323
]
Billy Pearson commented on HBASE-64:
------------------------------------
I thank HBASE-745 did basically what I was looking for above when HBASE-775 is
resolved this issue should be closed.
the only other item above or I had idea of was changeing the order of
compaction to the one with the most map files first.
With the speed gain from HBASE-745 I do not thank that is needed even if we had
100 regions per server compaction would keep up now I thank.
So unless anyone else is seeing backlogs in the compaction's now I thank the
compaction's bottlenecks have been solved.
> Add max number of mapfiles to compact at one time giveing us a minor & major
> compaction
> ---------------------------------------------------------------------------------------
>
> Key: HBASE-64
> URL: https://issues.apache.org/jira/browse/HBASE-64
> Project: Hadoop HBase
> Issue Type: Improvement
> Components: regionserver
> Reporter: Billy Pearson
> Priority: Minor
> Attachments: flag-v2.patch, flag.patch, twice.patch
>
>
> 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.
