[HBASE-6312] Make BlockCache eviction thresholds configurable

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 0.94.0
• Fix Version/s: 0.95.0
• Component/s: io
• Hadoop Flags: Reviewed

Release Note

From now on, the block cache will use all the memory it's given as its upper bound was raised from 85% to 99%. The lower bound for evictions, called "minimum factor", was raised from 75% to 95% and is now configurable via "hbase.lru.blockcache.min.factor". This means that 4% of the block cache is evicted at a time instead of 10%, so evictions may run more often but each will be less disruptive.

• Assignee: Jie Huang
• Reporter: Jie Huang
• Created: 03/Jul/12 06:07
• Updated: 23/Sep/13 18:30
• Resolved: 19/Jul/12 21:51

Description

Some of our customers found that tuning the BlockCache eviction thresholds made test results different in their test environment. However, those thresholds are not configurable in the current implementation. The only way to change those values is to re-compile the HBase source code. We wonder if it is possible to make them configurable.

Issue Links

• relates to: HBASE-7033 Add hbase.lru.blockcache.acceptable.factor to configuration, akin to the min.factor added by HBASE-6312
• relates to: HBASE-7053 port blockcache configurability (part of HBASE-6312, and HBASE-7033) to 0.94