hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Guanghao Zhang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-15504) Fix Balancer in 1.3 not moving regions off overloaded regionserver
Date Thu, 14 Apr 2016 01:23:25 GMT

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

Guanghao Zhang commented on HBASE-15504:

It's my fault. If maxMoves is much less than cluster regions number, move cost will be much
larger after HBASE-14604.
bq.That results in less IO spikes, fewer spikes to meta, and more reliability.
Yeah. We add throttling for region balance in our production cluster, e.g. balance one region
per second. So we didn't config hbase.master.balancer.stochastic.maxMovePercent very small.
Anyway, +1 for this patch.

> Fix Balancer in 1.3 not moving regions off overloaded regionserver
> ------------------------------------------------------------------
>                 Key: HBASE-15504
>                 URL: https://issues.apache.org/jira/browse/HBASE-15504
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 1.3.0
>            Reporter: Elliott Clark
>            Assignee: Elliott Clark
>             Fix For: 2.0.0, 1.3.0, 1.4.0
>         Attachments: HBASE-15504-v3.patch
> We pushed 1.3 to a couple of clusters. In some cases the regions were assigned VERY un-evenly
and the regions would not move after that.
> We ended up with one rs getting thousands of regions and most servers getting 0. Running
balancer would do nothing. The balancer would say that it couldn't find a solution with less
than the current cost.

This message was sent by Atlassian JIRA

View raw message