Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 18 Jun 2014 22:12:25 +0000 (UTC)
From: "Lars Hofhansl (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12721519.1402954944634.3711.1403129545171@arcas>
In-Reply-To: <JIRA.12721519.1402954944634@arcas>
References: <JIRA.12721519.1402954944634@arcas>
Subject: [jira] [Commented] (HBASE-11364) [BlockCache] Add a flag to cache
 data blocks in L1 if multi-tier cache
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Lars Hofhansl commented on HBASE-11364:
---------------------------------------

Belated +1

So this implies that storage will be L2 by default and L1 is opt in?
In the interested of the least surprise we might want to reverse that...?

> [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
(v6.2#6252)