hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jean-Daniel Cryans (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-4374) Up default regions size from 256M to 1G
Date Fri, 14 Oct 2011 20:24:11 GMT

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

Jean-Daniel Cryans commented on HBASE-4374:

bq. In old days there used to be an optimal balance to be struck between flush size, compaction
size and region split size. 

IMO something that radically screws this up is compression. I've been experimenting with 2GB
memstore flush size on a LZO'd table and saw radically better write performance.

I think it would be good that we bring the flush size up as we bring up the split size, since
this means less regions per RS leaving room for bigger and more efficient Memstores.
> Up default regions size from 256M to 1G
> ---------------------------------------
>                 Key: HBASE-4374
>                 URL: https://issues.apache.org/jira/browse/HBASE-4374
>             Project: HBase
>          Issue Type: Task
>            Reporter: stack
>            Priority: Blocker
>             Fix For: 0.92.0
> HBASE-4365 has some discussion of why we default for a table should tend to fewer bigger
regions.  It doesn't look like this issue will be done for 0.92.  For 0.92, lets up default
region size from 256M to 1G and talk up pre-split on table creation in manual.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message