Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Sat, 15 Feb 2014 01:54:21 +0000 (UTC)
From: "Hudson (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12694457.1392114369340.47881.1392429261150@arcas>
In-Reply-To: <JIRA.12694457.1392114369340@arcas>
References: <JIRA.12694457.1392114369340@arcas>
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


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

Hudson commented on HBASE-10498:
--------------------------------

FAILURE: Integrated in HBase-TRUNK-on-Hadoop-1.1 #90 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-1.1/90/])
HBASE-10498 Add new APIs to load balancer interface(Rajesh) (rajeshbabu: rev 1568188)
* /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/master/AssignmentManager.java
* /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/master/LoadBalancer.java
* /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/master/balancer/BaseLoadBalancer.java


> 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.98.1, 0.99.0
>
>         Attachments: HBASE-10498.patch
>
>
> 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)