[
https://issues.apache.org/jira/browse/HBASE-6312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13406553#comment-13406553
]
Jason Dai commented on HBASE-6312:
----------------------------------
If we do not expose the acceptable factor and minimum factor, the
hfile.block.cache.size parameter can be very confusing (for the user to
properly configure the cache size behavior). Just as J-D mentioned, if the user
want 2GB cache, he needs to set the parameter to ~2.35GB, and he needs to
understand the HBase implementation details to do that. This looks a lot like
hacking, not a user friendly interface. Maybe We should evict only after cache
size is large than hfile.block.cache.size, and allow ~15% burstiness before
blocking.
> 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
