Hi Abe, I believe at this time we only have the APIs for merging two regions in a single merge operation. Adding the ability to merge all regions within a row key range was a feature discussed recently. A compaction should not be necessary following a merge, however it is likely that the number of store files in the resulting region will trigger one. Have a look at HBASE-13103 for some thoughts on bring region size under management of the Master, similar to region placement. Your thoughts based on your use-case would be valuable over there.
Thanks, Nick https://issues.apache.org/jira/browse/HBASE-13103 On Mon, Mar 23, 2015 at 6:54 AM, Abe Weinograd <a...@flonet.com> wrote: > Hello, > > We bulk load our table and during that process, pre-split regions to > optimize load across servers. The number of regions build up and we > manually are merging them back. Any merge of two regions is causing a > compaction which slows down our merge process. > > We are merging two regions at a time and this it ends up being pretty > slow. In order to make it merge more regions in a shorter window of time, > should we be merging more than one? Can we do that? The reason we are > doing this is that our key is sequential. In the short term, changing it > is not an option. The merging helps keep the # of total regions down so > that when we create 20 new regions for a load, the balancer will spread out > the new regions across multiple region servers. > > We are currently on HBase 0.98.6 (CDH 5.3.0) > > Thanks, > Abe >
