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

Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2014/07/24 02:22:38 UTC

[jira] [Updated] (HBASE-11581) Add option so CombinedBlockCache L2 can be null (fscache)

     [ https://issues.apache.org/jira/browse/HBASE-11581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack updated HBASE-11581:
--------------------------

    Attachment: 11581.txt

> Add option so CombinedBlockCache L2 can be null (fscache)
> ---------------------------------------------------------
>
>                 Key: HBASE-11581
>                 URL: https://issues.apache.org/jira/browse/HBASE-11581
>             Project: HBase
>          Issue Type: New Feature
>          Components: BlockCache
>            Reporter: stack
>            Priority: Minor
>         Attachments: 11581.txt
>
>
> Add option, mostly for comparison's sake, that allows a deploy orchestrated by CombinedBlockCache such that its L1 is LruBlockCache for META blocks but DATA blocks are fetched each time (we don't try and cache them, no blockcache churn).
> In operation, i can see fscache coming around to cover the fetched DATA blocks such that if the DATA blocks fit in fscache, seeks go to zero.
> This setup for sure runs slower.  Will publish numbers elsewhere.  Meantime, here is a patch to enable this option.



--
This message was sent by Atlassian JIRA
(v6.2#6252)