hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jean-Daniel Cryans (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HBASE-5386) [usability] Soft limit for eager region splitting of young tables
Date Fri, 03 May 2013 20:18:15 GMT

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

Jean-Daniel Cryans resolved HBASE-5386.

    Resolution: Duplicate

We actually did this in 0.94 where we split early when a RS has a few regions from a table.
> [usability] Soft limit for eager region splitting of young tables
> -----------------------------------------------------------------
>                 Key: HBASE-5386
>                 URL: https://issues.apache.org/jira/browse/HBASE-5386
>             Project: HBase
>          Issue Type: New Feature
>          Components: Usability
>            Reporter: Jean-Daniel Cryans
> Coming out of HBASE-2375, we need a new functionality much like hypertable's where we
would have a lower split size for new tables and it would grow up to a certain hard limit.
This helps usability in different ways:
>  - With that we can set the default split size much higher and users will still have
good data distribution
>  - No more messing with force splits
>  - Not mandatory to pre-split your table in order to get good out of the box performance
> The way Doug Judd described how it works for them, they start with a low value and then
double it every time it splits. For example if we started with a soft size of 32MB and a hard
size of 2GB, it wouldn't be until you have 64 regions that you hit the ceiling.
> On the implementation side, we could add a new qualifier in .META. that has that soft
limit. When that field doesn't exist, this feature doesn't kick in. It would be written by
the region servers after a split and by the master when the table is created with 1 region.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message