Details
-
Task
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
-
None
Description
For hbase 2.0 release, there is correlation between the following parameters:
- hbase.memstore.inmemoryflush.threshold.factor : threshold for the active segment
- hbase.hregion.compacting.pipeline.segments.limit : pipeline length
For SSD, a threshold of 2% for the active segment (hbase.memstore.inmemoryflush.threshold.factor=0.02) and pipeline length of 4 (hbase.hregion.compacting.pipeline.segments.limit=4).
For HDD, hbase.hregion.compacting.pipeline.segments.limit should be 3 (due to lower throughput of HDD).