hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-9399) Up the memstore flush size
Date Tue, 24 Dec 2013 23:13:51 GMT

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

Andrew Purtell updated HBASE-9399:
----------------------------------

    Fix Version/s:     (was: 0.98.0)

bq. I finally got to try this and upping the memstore flush size to 512mb gave us about a
1% perf gain when running our IT tests. Nothing huge so we can take it or leave it.

Ok, moving out of 0.98

> Up the memstore flush size
> --------------------------
>
>                 Key: HBASE-9399
>                 URL: https://issues.apache.org/jira/browse/HBASE-9399
>             Project: HBase
>          Issue Type: Task
>          Components: regionserver
>    Affects Versions: 0.98.0, 0.96.0
>            Reporter: Elliott Clark
>            Assignee: Elliott Clark
>
> As heap sizes get bigger we are still recommending that users keep their number of regions
to a minimum.  This leads to lots of un-used memstore memory.
> For example I have a region server with 48 gigs of ram.  30 gigs are there for the region
server.  This with current defaults the global memstore size reserved is 8 gigs.
> The per region memstore size is 128mb right now.  That means that I need 80 regions actively
taking writes to reach the global memstore size.  That number is way out of line with what
our split policies currently give users.  They are given much fewer regions by default.
> We should up the hbase.hregion.memstore.flush.size size.  Ideally we should auto tune
everything.  But until then I think something like 512mb would help a lot with our write throughput
on clusters that don't have several hundred regions per RS.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message