[
https://issues.apache.org/jira/browse/HBASE-6312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13407624#comment-13407624
]
Jean-Daniel Cryans commented on HBASE-6312:
-------------------------------------------
I'm -1 on evicting past the cache size rather than before we reach it, I think
it's just reversing the problem since now we'd always use more memory than
we're supposed to. I always prefer to err on the side of caution.
Now if someone wants to set their acceptable and minimum factors > 1.0 then
it's their choice but in the end that doesn't change anything since you can
just set a bigger hfile.block.cache.size and have the same effect. Having all
those levers is not a good user experience IMO.
> 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
> Priority: Minor
> Attachments: hbase-6312.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
