Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-dev@hadoop.apache.org
Message-ID: <1968653003.10111264184183197.JavaMail.jira@brutus.apache.org>
Date: Fri, 22 Jan 2010 18:16:23 +0000 (UTC)
From: "stack (JIRA)" <jira@apache.org>
To: hbase-dev@hadoop.apache.org
Subject: [jira] Commented: (HBASE-2149)
 hbase.regionserver.global.memstore.lowerLimit is too low
In-Reply-To: <1397456270.375871264016334411.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

stack commented on HBASE-2149:
------------------------------

For RC3, do we just want to change the hbase-default lower limit?

> hbase.regionserver.global.memstore.lowerLimit is too low
> --------------------------------------------------------
>
>                 Key: HBASE-2149
>                 URL: https://issues.apache.org/jira/browse/HBASE-2149
>             Project: Hadoop HBase
>          Issue Type: Bug
>            Reporter: Jean-Daniel Cryans
>            Assignee: Jean-Daniel Cryans
>             Fix For: 0.20.4, 0.21.0
>
>
> The default value of hbase.regionserver.global.memstore.lowerLimit of 25% is very wrong and in almost all cases was problematic (I've seen this in at least 3 occurrences). The cost of flushing a memstore is fairly high and when the global size reaches 40% then ALL inserts are blocked. This means that with a heap of 1GB you could be flushing for 10-20 seconds or worse.
> I suggest a default setting of 38% or even 40% so that only a region or two will be flushed (the biggest ones) for maximum availability.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.