You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Biju Nair (JIRA)" <ji...@apache.org> on 2017/06/02 04:53:05 UTC

[jira] [Commented] (HBASE-18138) HBase named read caches

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

Biju Nair commented on HBASE-18138:
-----------------------------------

The current {{LruBlockCache/BucketCache}} implementations can be modified to support named caches with the current state to be cache named {{default}}. Attached has some quick changes for {{LruBlockCache}} made to see how complex the changes would be.

> HBase named read caches
> -----------------------
>
>                 Key: HBASE-18138
>                 URL: https://issues.apache.org/jira/browse/HBASE-18138
>             Project: HBase
>          Issue Type: New Feature
>          Components: BlockCache, BucketCache
>            Reporter: Biju Nair
>         Attachments: HBASE-18138.txt
>
>
> Instead of a single read(block) cache, if HBase can support creation of named read caches and use by tables it will help common scenarios like
> - Assigning a chunk of the cache to tables with data which are critical to performance so that they don’t get swapped out due to other less critical table data being read
> - To be able to guarantee a percentage of the cache to tenants in a multi tenant environment by assigning named caches to each tenant



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)