hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Subbu M Iyer (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-3658) Alert when heap is over committed
Date Fri, 18 Mar 2011 02:27:29 GMT

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

Subbu M Iyer commented on HBASE-3658:
-------------------------------------

Here is what we would do:

1. At the time of RS startup we examine the heap settings from config for the following config
settings:
a) hbase.regionserver.global.memstore.upperLimit
b) hfile.block.cache.size

If some of a+b is say 80% of heap (assuming we need additional 0.2 to do other household chores),
we abort the RS with appropriate error message.

c) Do we also need an additional config setting to declare default minimum we need to household
chores?

Please let me know.
 

> Alert when heap is over committed
> ---------------------------------
>
>                 Key: HBASE-3658
>                 URL: https://issues.apache.org/jira/browse/HBASE-3658
>             Project: HBase
>          Issue Type: Improvement
>    Affects Versions: 0.90.1
>            Reporter: Jean-Daniel Cryans
>             Fix For: 0.92.0
>
>
> Something I just witnessed, the block cache setting was at 70% but the max global memstore
size was at the default of 40% meaning that 110% of the heap can potentially be "assigned"
and then you need more heap to do stuff like flushing and compacting.
> We should run a configuration check that alerts the user when that happens and maybe
even refuse to start.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message