You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Anoop Sam John (JIRA)" <ji...@apache.org> on 2016/04/11 06:58:25 UTC

[jira] [Commented] (HBASE-15625) Make minimum values configurable and smaller

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

Anoop Sam John commented on HBASE-15625:
----------------------------------------

In another attempt, we want to make use of off heap memory for the bigger parts like BC and Memstore.  So we want to work with lower heap size only. JFYI.
For BC there can be even 0 size.  For memstore at least 5% memory is what we mandate as per code as of now.

> 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: Asher Bartch
>            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)