hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Hsieh (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-11581) Add option so CombinedBlockCache L2 can be null (fscache)
Date Thu, 24 Jul 2014 21:34:38 GMT

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

Jonathan Hsieh commented on HBASE-11581:

looks fine.  Is the idea just for specialized benchmarking?

 Is there an easy way to get unit tests to exercise this new config?

> 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
>            Assignee: 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

View raw message