hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Konstantin Ryakhovskiy (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-15625) Make minimum values configurable and smaller
Date Tue, 26 Jul 2016 19:38:21 GMT

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

Konstantin Ryakhovskiy commented on HBASE-15625:
------------------------------------------------

[~asher] are you working on this issue?
If not, can I re-assign and submit the patch?
Thanks

> 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)

Mime
View raw message