[
https://issues.apache.org/jira/browse/HBASE-10576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13977821#comment-13977821
]
ramkrishna.s.vasudevan commented on HBASE-10576:
------------------------------------------------
bq.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.
This suggestion is excellent.
Few doubts on the opening of index region
Which hook we will be using to open a a corresponding index region? So the
opening of a main region would be considered done only if the index region
(virually) gets opened in the hosting RS? If not we would consider the region
opening/closing as a failure right?
The datastructures that holds the active regions should be updated still and
those things may need some changes in the core or add some new hooks to suppor
them.
I think the suggestion has got lot of advantages, just that need to see how it
turns out. +1 on this suggestion.
> 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)
