You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Bryan Duxbury (JIRA)" <ji...@apache.org> on 2008/06/19 18:31:45 UTC

[jira] Resolved: (HBASE-615) Region balancer oscillates during cluster startup

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

Bryan Duxbury resolved HBASE-615.
---------------------------------

    Resolution: Fixed

I just committed this.

> Region balancer oscillates during cluster startup
> -------------------------------------------------
>
>                 Key: HBASE-615
>                 URL: https://issues.apache.org/jira/browse/HBASE-615
>             Project: Hadoop HBase
>          Issue Type: Bug
>          Components: master
>    Affects Versions: 0.2.0
>            Reporter: Jim Kellerman
>            Assignee: Bryan Duxbury
>            Priority: Blocker
>             Fix For: 0.2.0
>
>         Attachments: 615-lite.patch, 615-v2.patch
>
>
> When starting a cluster with four region servers and a large table (49 regions) (+root +meta) = 51 total regions, the region balancer oscillates for a very long time and does not seem to reach a steady state.
> Additionally, for whatever reason, it seems reluctant to assign regions to the first of four region servers, which may be the root cause. In my test, the first server had 10 regions assigned, the second and fourth had 13 regions assigned, and the master would continually assign and deassign 2 regions to the third server, which oscillated between 13 and 15 regions.  If it assigned the two fluctuating regions to the first server, it would achieve the best balance possible: 12, 13, 13, 13.
> After 20 minutes, it had not stopped oscillating. An application trying to work against this cluster would run very slowly as it would be continually re-finding the two regions in flux.
> When the table was being created, regions were nicely balanced. On restart, however, it just would not settle down.
> Perhaps the balancer should set a target number of regions for each server which when the server achieved +/- 1 regions, the rebalancer would not try to change unless the number of regions changed.

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