hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Hofhansl (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-11364) [BlockCache] Add a flag to cache data blocks in L1 if multi-tier cache
Date Thu, 19 Jun 2014 20:00:26 GMT

    [ https://issues.apache.org/jira/browse/HBASE-11364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14037773#comment-14037773

Lars Hofhansl commented on HBASE-11364:

Yeah option #1.
* Have config in hbase-site.xml to enable the bucketcache (default off)
* when bucket cache is enabled via config it is the default (not schema changes required)
* folks can selectively pull tables into L1 only via a schema change

We can also make the config option default on going forward. That'd be almost identical to
your option #2, only that it could disabled via a config. But maybe we do not want more configs?

#3 will be incredibly hard to get right for all cases and lead to double caching and potentially
even more GC as we churn blocks through L2 to L1 and back.

> [BlockCache] Add a flag to cache data blocks in L1 if multi-tier cache
> ----------------------------------------------------------------------
>                 Key: HBASE-11364
>                 URL: https://issues.apache.org/jira/browse/HBASE-11364
>             Project: HBase
>          Issue Type: Task
>            Reporter: stack
>            Assignee: stack
>             Fix For: 0.99.0
>         Attachments: 11364.txt
> This is a prerequisite for HBASE-11323 BucketCache on all the time.  It addresses a @lars
hofhansl ask that we be able to ask that for some column families, even their data blocks
get cached up in the LruBlockCache L1 tier in a multi-tier deploy as happens when doing BucketCache
(CombinedBlockCache) setups.

This message was sent by Atlassian JIRA

View raw message