hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nick Dimiduk (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-14189) BlockCache options should consider CF Level BlockCacheEnabled setting
Date Mon, 10 Aug 2015 17:15:46 GMT

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

Nick Dimiduk commented on HBASE-14189:

bq. they are useless for the whole RS cache setting

Hi [~chenheng]. The current layered approach is the way it is because we get global controls
with local overrides. For instance, when I have as much memory as I expect to have data, cacheonwrite
makes sense as a global setting. Can you elaborate on the above? It's an opinion, not really
much reasoning to convince the rest of us.

> BlockCache options should consider CF Level BlockCacheEnabled setting
> ---------------------------------------------------------------------
>                 Key: HBASE-14189
>                 URL: https://issues.apache.org/jira/browse/HBASE-14189
>             Project: HBase
>          Issue Type: Improvement
>          Components: BlockCache
>    Affects Versions: 2.0.0
>            Reporter: Heng Chen
>            Assignee: Heng Chen
>         Attachments: HBASE-14189.patch
> While using BlockCache,  we use {{cacheDataOnRead}}({{cacheDataOnWrite}}) represents
for whether we should cache block after read(write) block from(to) hdfs.  We should honour
BC setting and CF Level cache setting while using BlockCache.

This message was sent by Atlassian JIRA

View raw message