[
https://issues.apache.org/jira/browse/HBASE-15625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Junegunn Choi resolved HBASE-15625.
-----------------------------------
Resolution: Fixed
> Make minimum values configurable and smaller
> --------------------------------------------
>
> Key: HBASE-15625
> URL: https://issues.apache.org/jira/browse/HBASE-15625
> Project: HBase
> Issue Type: Improvement
> Affects Versions: 1.2.0
> Reporter: Jean-Marc Spaggiari
> Assignee: JinHyuk Kim
> Priority: Minor
> Labels: beginner, pull-request-available
> Fix For: 2.7.0, 3.0.0-beta-2, 2.6.4, 2.5.13
>
>
> 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.10#820010)
