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 9A9291006C for ; Tue, 11 Feb 2014 17:15:23 +0000 (UTC) Received: (qmail 1412 invoked by uid 500); 11 Feb 2014 17:15:20 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 1331 invoked by uid 500); 11 Feb 2014 17:15:19 -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 1311 invoked by uid 99); 11 Feb 2014 17:15:19 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Feb 2014 17:15:19 +0000 Date: Tue, 11 Feb 2014 17:15:19 +0000 (UTC) From: "James Taylor (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-10498) Add new APIs to load balancer interface 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-10498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13898035#comment-13898035 ] James Taylor commented on HBASE-10498: -------------------------------------- Can this work be done in 0.98? > Add new APIs to load balancer interface > --------------------------------------- > > Key: HBASE-10498 > URL: https://issues.apache.org/jira/browse/HBASE-10498 > Project: HBase > Issue Type: Improvement > Components: Balancer > Reporter: rajeshbabu > Assignee: rajeshbabu > Fix For: 0.99.0 > > > If a custom load balancer required to maintain region and corresponding server locations, > we can capture this information when we run any balancer algorithm before assignment(like random,retain). > But during master startup we will not call any balancer algorithm if a region already assinged > During split also we open child regions first in RS and then notify to master through zookeeper. > So split regions information cannot be captured into balancer. > Since balancer has access to master we can get the information from online regions or region plan data structures in AM. > But some use cases we cannot relay on this information(mainly to maintain colocation of two tables regions). > So it's better to add some APIs to load balancer to notify balancer when *region is online or offline*. > These APIs helps a lot to maintain *regions colocation through custom load balancer* which is very important in secondary indexing. -- This message was sent by Atlassian JIRA (v6.1.5#6160)