[
https://issues.apache.org/jira/browse/HBASE-10576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13977655#comment-13977655
]
Jeffrey Zhong commented on HBASE-10576:
---------------------------------------
I have different proposal to ensure data & index table colocate on the same RS.
The high level idea(shadow region) is listed below:
1) Every time when we open a data region, we use coprocessor to open the index
region.
2) When we close a data region, the same coprocessor closes the index region
3) The index region(shadow region) won't recorded in meta table so AM won't
assign them so there is no need to implement custom load balancer.
4) Index region is still visible by hosting region server and corresponding
statistics matrix
Client can use region location of data table to talk to its corresponding index
region because of colocation. The suggestion simplifies implementation and the
good part guarantees index region always opened along with data region. No edge
cases such as we can open one but not the other or become online in different
order.
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)
