I was reading an old thriller, "HBASE-3149 Make flush decisions per column family", and I got to the good bit where our NicolasS argues that per-CF flush is likely not needed because small files is fine actually as long as these small files are hoovered up quckly. He mentioned the hbase.hstore.compaction.min.size config which we'd set to be equal to flush size and he argued that our default should be much lower -- 1/16th smaller -- so we always get rid of the small files first.
The config. was removed here: Author: Zhihong Yu <[email protected]> 2012-10-30 13:14:01 Committer: Zhihong Yu <[email protected]> 2012-10-30 13:14:01 Parent: 2c0261b4e6571d627fb017338aeaf10089b75dab (HBASE-7060 Region load balancing by table does not handle the case where a table's region count is lower than the number of the RS in the cluster (Ted Yu and Tianying)) Child: 7380036d88ed6c6ddfad4f4fc2ef617ab419d610 (HBASE-7055 port HBASE-6371 tier-based compaction from 0.89-fb to trunk - revert for further discussion) Branches: many (31) Follows: Precedes: HBASE-7055 port HBASE-6371 tier-based compaction from 0.89-fb to trunk (Sergey) I was wondering if w/ our new compaction algos if we are making use of NicolasS's advice (informed by experience) or not? Thanks, St.Ack
