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-11938) Unify cache configuration
Date Wed, 10 Sep 2014 22:45:35 GMT

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

Nick Dimiduk commented on HBASE-11938:
--------------------------------------

Related to HBASE-10403 but larger than just bucketcache.

> Unify cache configuration
> -------------------------
>
>                 Key: HBASE-11938
>                 URL: https://issues.apache.org/jira/browse/HBASE-11938
>             Project: HBase
>          Issue Type: Improvement
>          Components: regionserver
>            Reporter: Nick Dimiduk
>            Priority: Minor
>
> As pointed out in a [comment|https://issues.apache.org/jira/browse/HBASE-11331?focusedCommentId=14128811&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14128811]
on HBASE-11331, our configuration keys for the blockcache are all over the place.
> {quote}
> There's not a lot of consistency around cache configurations. We also have:
>  - hbase.rs.cacheblocksonwrite
>  - hfile.block.index.cacheonwrite
>  - hfile.block.bloom.cacheonwrite
>  - hbase.rs.evictblocksonclose
>  - hbase.bucketcache.*
>  - hbase.rs.prefetchblocksonopen
>  - hbase.offheapcache.minblocksize
> {quote}
> We should rename them to a consistent scheme.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message