[
https://issues.apache.org/jira/browse/HBASE-10576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13980824#comment-13980824
]
rajeshbabu commented on HBASE-10576:
------------------------------------
[~stack]
bq. Please tell me more how this balancer works. It is not clear skimming the
code. 'colocate' is how you term data and index tables going together?
Main idea of the balancer is to select same plan for a user region and it's
corresponding index region at any time.
The custom balancer is wrapper on top of normal balancer like
StochasticLoadBalancer(which will be used as delegator).
The balancer maintains the region plans of user table and corresponding index
table in a map.We call it as co-location info.
When AM requests for a user(index) regions plans first we will check any plans
available for corresponding index(user) regions in the co-location info.
If available same will be selected as plans otherwise generate the plans in any
fashion like round-robin/random/retain by the delegator and add them
to co-location info.
When a region is offline the corresponding region plan will be removed from the
co-location info.
Thanks.
> Custom load balancer to co-locate the regions of two tables which are having
> same split keys
> --------------------------------------------------------------------------------------------
>
> Key: HBASE-10576
> URL: https://issues.apache.org/jira/browse/HBASE-10576
> Project: HBase
> Issue Type: Sub-task
> Components: Balancer
> Reporter: rajeshbabu
> Assignee: rajeshbabu
> Attachments: HBASE-10536_v2.patch, HBASE-10576.patch
>
>
> To support local indexing both user table and index table should have same
> split keys. This issue to provide custom balancer to colocate the regions of
> two tables which are having same split keys.
> This helps in Phoenix as well.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
