[
https://issues.apache.org/jira/browse/HBASE-26147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17393431#comment-17393431
]
Josh Elser commented on HBASE-26147:
------------------------------------
Just so folks see it who are interested, I just left Bryan at
[comment|https://github.com/apache/hbase/pull/3536/files#r682925736] indicating
that I would prefer a new {{balance}} method on {{Admin}} which can have a
{{Public}} but {{Evolving}} object (Bryan suggested {{BalancerConfig}} which
seems like a reasonable name), which can encapsulate the different ways to run
the balancer. I think that strikes a nice balance (no pun intended) between
satisfying this use case without causing big changes in this otherwise fairly
stable interface.
> Add dry run mode to hbase balancer
> ----------------------------------
>
> Key: HBASE-26147
> URL: https://issues.apache.org/jira/browse/HBASE-26147
> Project: HBase
> Issue Type: Improvement
> Components: Balancer, master
> Reporter: Bryan Beaudreault
> Assignee: Bryan Beaudreault
> Priority: Major
>
> It's often rather hard to know how the cost function changes you're making
> will affect the balance of the cluster, and currently the only way to know is
> to run it. If the cost decisions are not good, you may have just moved many
> regions towards a non-ideal balance. Region moves themselves are not free for
> clients, and the resulting balance may cause a regression.
> We should add a mode to the balancer so that it can be invoked without
> actually executing any plans. This will allow an administrator to iterate on
> their cost functions and used the balancer's logging to see how their changes
> would affect the cluster.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
