If you make the table metadata change that Stack describes, it will permanently apply to that particular table, even after shutdown/restart, but only that one table.
Changing the global config parameter 'hbase.hregion.max.filesize' affects any tables already existing or yet to be created. - Andy > From: stack > Subject: Re: Load Balancing problem for HBase to host data in > small size under high load > To: [email protected] > Date: Friday, September 26, 2008, 8:18 AM > Jean-Daniel Cryans wrote: > > Zhou, > > > > No sorry there is no guide tho I'm sure that > > searching through this mailing > > list you would find some answers. > > I just happened to be looking into this last night (smile). > > To bring on a split, try the following: > > 1. Set down the hbase.region.memcache.flush.size on your > table. There is a bug that prevents you making this adjustment > from the shell at the moment but for a workaround, see > https://issues.apache.org/jira/browse/HBASE-903. > 2. Then, wait till the optional flush runs > (hbase.regionserver.optionalcacheflushinterval). Default is > every 30 minutes. > > If you want to run permanently with the smaller split size, > you should do as you posit, and lower the flush size -- > hbase.hregion.memcache.flush.size -- in same proportion by > which you lowered split size. > > St.Ack
