[
https://issues.apache.org/jira/browse/HBASE-4464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13258020#comment-13258020
]
Uma Maheswara Rao G commented on HBASE-4464:
--------------------------------------------
One idea is, Balancer can populate the Region plans into Queue from
LoadBalancer.
HMaster can initiate one thread to process the balancer plans queque. So,
whenever balancer finalize one plan object, it will put into that queue.
BalancerQueueProcessor(thread) can pick the plans from queue and process. But
the current LoadBalancer interface does not take any queue. It will just return
List of plans from balanceCluster api. Changing interface may be difficult, as
the LoadBalancer is exposed one. Any alternatives without changing interface?
> Make region balancing parallel with balancer.balanceCluster()
> -------------------------------------------------------------
>
> Key: HBASE-4464
> URL: https://issues.apache.org/jira/browse/HBASE-4464
> Project: HBase
> Issue Type: Improvement
> Reporter: Ted Yu
>
> balancer.balanceCluster() generates RegionPlans for HMaster.balance() to
> execute.
> We don't retract any RegionPlan in balancer.balanceCluster().
> In the near future, more complex algorithm would be introduced to try
> achieving maximum block location affinity for the regions to be moved. This
> means balancer.balanceCluster() would take longer to return.
> This JIRA makes region balancing parallel with balancer.balanceCluster()
> Meaning region balancing would be performed when balancer.balanceCluster() is
> still running.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
