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

Posted to issues@hbase.apache.org by "Nicolas Spiegelberg (JIRA)" <ji...@apache.org> on 2011/07/14 01:12:59 UTC

[jira] [Commented] (HBASE-862) region balancing is clumsy

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

Nicolas Spiegelberg commented on HBASE-862:
-------------------------------------------

We got bit by this in our 89 branch a couple weeks back.  Looking at the trunk and I don't see "hbase.regions.close.max" anywhere?  Is this still an issue?  What are we doing to limit regionsToMove.size()?

> region balancing is clumsy
> --------------------------
>
>                 Key: HBASE-862
>                 URL: https://issues.apache.org/jira/browse/HBASE-862
>             Project: HBase
>          Issue Type: Bug
>            Reporter: stack
>
> Daniel Leffel has an install of 500 regions on 4 nodes.  He's running 0.2.0.
> On restart, load balancing is running while the 600 regions are being initially opened.  Makes for churn.  Load balancing should wait before it cuts in.
> Have also seen on occasion that it will not find equilibrium after a restart.
> Adding a node is catastrophic.  >20% of the regions were closed and were taking the longest time to show up on the new server.  I would think that the region balancing would work in more sophisticated and gradual manner.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira