[
https://issues.apache.org/jira/browse/HBASE-15625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15821175#comment-15821175
]
Sean Busbey commented on HBASE-15625:
-------------------------------------
Reassigned to you [~ryakhovskiy.k]. Please attach a patch for master.
Also some quick feedback on the patch:
1) We'd really like to avoid more constants in HConstants, so if you could
define these in a different place close to where they're used that'd be better.
2) HConstants is part of the public API and marked stable, so please make sure
the name {{HConstants.HBASE_CLUSTER_MINIMUM_MEMORY_THRESHOLD}} still points to
a float, and mark it deprecated so we can remove it in the future.
> 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
> Assignee: Konstantin Ryakhovskiy
> 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
(v6.3.4#6332)
