[
https://issues.apache.org/jira/browse/HBASE-10576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13977915#comment-13977915
]
rajeshbabu commented on HBASE-10576:
------------------------------------
[~jeffreyz]
I too thought the similar approach like opening and closing index regions
through coprocesors but not exactly like shadow region concept.
I thought many problems with this approach and so didn't propose it. One good
thing with this approach is we can guarantee 100% co-location.
Can you explain more how do we handle these?
1) How index table will be created? To avoid listing the index regions in meta
during table creation, do we need to divide the table creation into pieces and
just create directories/files needed for index table regions?
2) How to open the shadow regions if user regions already serving by some RS.
Do we need to send region open request from client(At present we cannot do
this) or user table should be disabled and enable back?
3) How do we find corresponding index region to be opened in coprocessors if we
dont have region info in META? some how from file system?
> 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)
