[
https://issues.apache.org/jira/browse/HBASE-6312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Daniel Cryans updated HBASE-6312:
--------------------------------------
Resolution: Fixed
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.
Hadoop Flags: Reviewed
Status: Resolved (was: Patch Available)
Closed the jira and added a release note.
> Make BlockCache eviction thresholds configurable
> ------------------------------------------------
>
> Key: HBASE-6312
> URL: https://issues.apache.org/jira/browse/HBASE-6312
> Project: HBase
> Issue Type: Improvement
> Components: io
> Affects Versions: 0.94.0
> Reporter: Jie Huang
> Assignee: Jie Huang
> Priority: Minor
> Fix For: 0.96.0
>
> Attachments: hbase-6312.patch, hbase-6312_v2.patch,
> hbase-6312_v3.patch
>
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
