Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 23 Apr 2014 04:45:21 +0000 (UTC)
From: "Anoop Sam John (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12696241.1392903524812.160715.1398228321157@arcas>
In-Reply-To: <JIRA.12696241.1392903524812@arcas>
References: <JIRA.12696241.1392903524812@arcas>
Subject: [jira] [Commented] (HBASE-10576) Custom load balancer to co-locate
 the regions of two tables which are having same split keys
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HBASE-10576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13977823#comment-13977823 ] 

Anoop Sam John commented on HBASE-10576:
----------------------------------------

Interesting ideas around.  One Q
bq.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
So what will happen when some one runs tools like HBCK?   We wont even create an index table?  

> 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)