I'd try that. Please come back with results. Also, if possible it will be useful (at least for the important jira mentioned by Nick) if you can share the stats on the regions (size, store files #) before and after the procedure. Note (as Lars said): "careful, this ... can put some load on the net/disks".
One more note: only increasing hbase.hregion.max.filesize may not help to completely avoid the same situation in future. It's hard to tell, but if you have what I'm thinking, I'd say data distribution pattern has greater affect. Though it will be mitigated to some extend by upping the region size. Alex Baranau -- http://cdap.io - open source framework to build and run data applications on Hadoop & HBase On Wed, Mar 11, 2015 at 7:00 PM, David chen <[email protected]> wrote: > hbase.store.delete.expired.storefile is true in file > hbase-0.98.5/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/compaction/CompactionConfigureation.java, > the reference code is 83th line as follows: > shouldDeleteExpired = > conf.getBoolean("hbase.store.delete.expired.storefile", true); > > > The region number have grown from 16 to 263 over the past seven months, > maybe the hbase.hregion.max.filesize value(4G) is a bit small. It looks > likely that the solution is to adjust hbase.hregion.max.filesize bigger and > merge the adjacent regions. > Any other ideas to suggest? > > > > > > > > >
