On Thu, Sep 16, 2010 at 9:32 AM, Jinsong Hu <[email protected]> wrote: > That means, if we run this in production system and key is chronological > order, we will end up > having thousands of regions as time goes on and the number of regions never > decrease, > even though old data are compacted away. we don't really mind having several > empty regions, but the fact that the region number continue to grow > unlimited without stop as time goes on, is really troublesome. It waste > hadoop namenode resource, and waste memory resource on regionserver, as each > region takes some memory to store region info. >
Agreed. It'd be easy enough to write a script to do this run out of cron but yeah, we should have a facility to sweep hbase and in particular if regions are empty of store files, merge to neighbour. Would you mind updating hbase-2999 to make it clear what is needed to satisfy the issue? The clearer the stipulation, the easier it is on the implementor (Patches also accepted if you'd like to have a go at this yourself). St.Ack
