Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 76AD711BD0 for ; Fri, 25 Apr 2014 04:51:27 +0000 (UTC) Received: (qmail 7477 invoked by uid 500); 25 Apr 2014 04:51:26 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 7133 invoked by uid 500); 25 Apr 2014 04:51:21 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 7109 invoked by uid 99); 25 Apr 2014 04:51:18 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 25 Apr 2014 04:51:18 +0000 Date: Fri, 25 Apr 2014 04:51:18 +0000 (UTC) From: "stack (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: 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 X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-10576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13980695#comment-13980695 ] stack commented on HBASE-10576: ------------------------------- bq. If current implementation can handle those similar corner cases from indeterministic nature of AM, I think current load balancer approach is also good. [~jeffreyz] I was going to say no but seems like @rajeshbabu can do it w/ his patch according to list above (Thanks for making the list). I see merit in your proposal now where shadow region is opened by a coprocessor (but otherwise is in the 'shadows' as far as the cluster is concerned -- no entry in hbase:meta). [~rajesh23] 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? We cannot hack up the core of hbase to get this feature in. 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)