You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Lars Hofhansl (Updated) (JIRA)" <ji...@apache.org> on 2011/10/27 01:57:32 UTC
[jira] [Updated] (HBASE-4683) Create config option to only cache
index blocks
[ https://issues.apache.org/jira/browse/HBASE-4683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars Hofhansl updated HBASE-4683:
---------------------------------
Description:
This would add a new boolean config option: hfile.block.cache.datablocks
Default would be true.
Setting this to false allows HBase in a mode where only index blocks are cached, which is useful for analytical scenarios where a useful working set of the data cannot be expected to fit into the cache.
This is the equivalent of setting cacheBlocks to false on all scans (including scans on behalf of gets).
I would like to general feeling about what folks think about this.
The change itself would be simple.
was:
This would add a new boolean config option: hfile.block.cache.datablocks
Default would be true.
Setting this to false allows HBase in a mode where only index blocks are cached, which is useful for analytical scenarios where a useful working set of the data cannot be expected to fit into the cache.
This is the equivalent of setting all cacheBlocks to false on all scans (including scans on behalf of gets).
I would like to general feeling about what folks think about this.
The change itself would be simple.
> Create config option to only cache index blocks
> -----------------------------------------------
>
> Key: HBASE-4683
> URL: https://issues.apache.org/jira/browse/HBASE-4683
> Project: HBase
> Issue Type: New Feature
> Reporter: Lars Hofhansl
> Priority: Minor
> Fix For: 0.94.0
>
>
> This would add a new boolean config option: hfile.block.cache.datablocks
> Default would be true.
> Setting this to false allows HBase in a mode where only index blocks are cached, which is useful for analytical scenarios where a useful working set of the data cannot be expected to fit into the cache.
> This is the equivalent of setting cacheBlocks to false on all scans (including scans on behalf of gets).
> I would like to general feeling about what folks think about this.
> The change itself would be simple.
--
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