[
https://issues.apache.org/jira/browse/HBASE-21338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-21338:
--------------------------
Resolution: Fixed
Hadoop Flags: Reviewed
Fix Version/s: (was: 2.1.2)
(was: 1.4.9)
(was: 1.5.0)
2.1.1
Release Note:
The description claims the balancer not dynamically configurable but this is an
error; it is http://hbase.apache.org/book.html#dyn_config
Also, if balancer is seen to be cutting out too soon, try setting
"hbase.master.balancer.stochastic.runMaxSteps" to true.
Adds cleaner logging around balancer start.
Status: Resolved (was: Patch Available)
> [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)
