You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2010/01/22 19:42:21 UTC

[jira] Resolved: (HBASE-2149) hbase.regionserver.global.memstore.lowerLimit is too low

     [ https://issues.apache.org/jira/browse/HBASE-2149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack resolved HBASE-2149.
--------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 0.20.4)
                   0.20.3
         Assignee: stack  (was: Jean-Daniel Cryans)
     Hadoop Flags: [Reviewed]

Committed branch and trunk the change of low limit from 0.25 to 0.35.  Opened HBASE-2158 to implement Ryans' suggestion.

> 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: stack
>             Fix For: 0.20.3, 0.21.0
>
>         Attachments: 2149.patch
>
>
> 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.