Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 17 Mar 2011 18:22:29 +0000 (UTC)
From: "Jonathan Gray (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: 
 <225999408.9656.1300386149582.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1075664717.7510.1300309109553.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] Commented: (HBASE-3658) Alert when heap is over committed
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jonathan Gray commented on HBASE-3658:
--------------------------------------

+1 on refusing to start

> 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