hbase.hstore.compactionThreshold is when to trigger a compaction. if > hbase.hstore.blockingStoreFiles in a Store, then we'll not take on any more writes until the number has been reduced (in actuality, we'll just pause writes a while in attempt at giving the server a breather, a chance to catch up on compactions).
A major compacts all files in a Store, regardless of the count. Minor compactions, the ones that usually run, will run a subset. hbase.hstore.compaction.max is the maximum to include in the subset when running a minor compaction (this config. is likely never used it would seem). Yes, Store used to be called HStore. The first two are actually very different attributes though. Hopefully above helps. Should I file an issue to improve their descriptions? Are they confusing? St.Ack On Fri, Jun 4, 2010 at 2:51 PM, Vidhyashankar Venkataraman <[email protected]> wrote: > Can you tell me the difference between hbase.hstore.compactionThreshold, > hbase.hstore.blockingStoreFiles and > hbase.hstore.compaction.max?The first two seem very similar in their > description (Store instead of Hstore).. > > Thank you > Vidhya >
