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/11 20:06:00 UTC
[jira] [Resolved] (HBASE-15625) Make minimum values configurable and smaller
[ https://issues.apache.org/jira/browse/HBASE-15625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Kyle Purtell resolved HBASE-15625.
-----------------------------------------
Assignee: (was: Konstantin Ryakhovskiy)
Resolution: Invalid
> Make minimum values configurable and smaller
> --------------------------------------------
>
> Key: HBASE-15625
> URL: https://issues.apache.org/jira/browse/HBASE-15625
> Project: HBase
> Issue Type: Bug
> Affects Versions: 1.2.0
> Reporter: Jean-Marc Spaggiari
> Priority: Minor
> Labels: beginner
>
> When we start a RS, we check HConstants.HBASE_CLUSTER_MINIMUM_MEMORY_THRESHOLD to make sure we always keep 20% of the heap for HBase (See below). In the past maximum heap size was about 20GB, which means 4GB for HBase.
> Today, with huge heaps and GC1, 20% gives a lot to HBase. Like with 80GB heap, it gives 16GB, which I think it not required.
> We need to make HBASE_CLUSTER_MINIMUM_MEMORY_THRESHOLD configurable and lower it's default value to 10%. It will not make any difference on any HBase configuration but will allow admins to be more flexible.
> Same thing for the minimum memstore and blockcache sizes.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)