Here're some other memstore related config parameters: hbase.regionserver.global.memstore.size hbase.regionserver.global.memstore.size.lower.limit hbase.hregion.preclose.flush.size hbase.hregion.memstore.block.multiplier
hbase.hregion.percolumnfamilyflush.size.lower.bound The last one is for per column family flush. You can find their meaning in either hbase-common/src/main/resources/hbase-default.xml or, in http://hbase.apache.org/book.html FYI On Sat, Aug 1, 2015 at 1:14 AM, Chang Chen <[email protected]> wrote: > Hi All > > How does HBase flush memstore besides the configuration in > [hbase.hregion.memstore.flush.size]? I believe we set flush size to 64M, > but I find many *small* memstore flush logs as below > > 2015-06-25 10:19:09,243 INFO org.apache.hadoop.hbase.regionserver.HRegion: > Finished memstore flush of ~69.8 K/71520, currentsize=0/0 for region > user_intent_exp,1696512044,1426251005088.448ddc0071414b6af5729e4476ea35e8. > in 26ms, sequenceid=18149727777, compaction requested=true > > 2015-06-25 10:20:54,428 INFO org.apache.hadoop.hbase.regionserver.HRegion: > Finished memstore flush of ~6.9 K/7104, currentsize=0/0 for region > user_intent_exp,472446392,1426251005088.8d6041bd68dd431f5840357a2fd8bce2. > in 30ms, sequenceid=18149728414, compaction requested=false > > > Is there any other configuration which can affect flush? Will HTable.close > cause it happen? > > Thanks > Chang >
