You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Andrew Kyle Purtell (Jira)" <ji...@apache.org> on 2022/06/17 17:14:00 UTC
[jira] [Resolved] (HBASE-11938) Unify cache configuration
[ https://issues.apache.org/jira/browse/HBASE-11938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Kyle Purtell resolved HBASE-11938.
-----------------------------------------
Resolution: Won't Fix
> 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
(v8.20.7#820007)