[
https://issues.apache.org/jira/browse/HBASE-21338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16680309#comment-16680309
]
Hudson commented on HBASE-21338:
--------------------------------
SUCCESS: Integrated in Jenkins build HBase-1.3-IT #500 (See
[https://builds.apache.org/job/HBase-1.3-IT/500/])
HBASE-21373 (backport from HBASE-21338) Warn if balancer is an ill-fit
(apurtell: rev 6f53424f8111b41fada49454d3bfe141007d9104)
* (edit)
hbase-server/src/main/java/org/apache/hadoop/hbase/master/balancer/StochasticLoadBalancer.java
> [balancer] If balancer is an ill-fit for cluster size, it gives little
> indication
> ---------------------------------------------------------------------------------
>
> Key: HBASE-21338
> URL: https://issues.apache.org/jira/browse/HBASE-21338
> Project: HBase
> Issue Type: Sub-task
> Components: Balancer, Operability
> Reporter: stack
> Assignee: Xu Cang
> Priority: Major
> Fix For: 3.0.0, 2.2.0, 2.1.1, 2.0.3
>
> Attachments: HBASE-21338.master.001.patch
>
>
> See parent issue. Running balancer on a cluster where the max steps was way
> inadequate, the balancer gave little to no indication that it was
> ill-configured. In fact, it only logged its starting and then that there was
> nothing to do though the cluster was obviously out-of-whack.
> Ideally the balancer would complain when say the maxSteps limit is a small
> fraction of what the cluster's calculated max steps are, or it would notice
> that the balancer is making little progress on an imbalanced cluster and
> shout. Can we set balancer configs w/o having to restart Master?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
