Return-Path: 
 <issues-return-37809-apmail-hbase-issues-archive=hbase.apache.org@hbase.apache.org>
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 1BCE099E1
	for <apmail-hbase-issues-archive@www.apache.org>;
 Fri,  2 Mar 2012 16:24:20 +0000 (UTC)
Received: (qmail 97514 invoked by uid 500); 2 Mar 2012 16:24:20 -0000
Delivered-To: apmail-hbase-issues-archive@hbase.apache.org
Received: (qmail 97484 invoked by uid 500); 2 Mar 2012 16:24:19 -0000
Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@hbase.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@hbase.apache.org>
List-Post: <mailto:issues@hbase.apache.org>
List-Id: <issues.hbase.apache.org>
Delivered-To: mailing list issues@hbase.apache.org
Received: (qmail 97475 invoked by uid 99); 2 Mar 2012 16:24:19 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Mar 2012 16:24:19 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=5.0
	tests=ALL_TRUSTED,T_RP_MATCHES_RCVD
X-Spam-Check-By: apache.org
Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Mar 2012 16:24:18 +0000
Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116])
	by hel.zones.apache.org (Postfix) with ESMTP id C71A65BB6
	for <issues@hbase.apache.org>; Fri,  2 Mar 2012 16:23:58 +0000 (UTC)
Date: Fri, 2 Mar 2012 16:23:58 +0000 (UTC)
From: "ramkrishna.s.vasudevan (Assigned) (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: 
 <303522788.12503.1330705438817.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1928279070.12396.1330703517915.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Assigned] (HBASE-5510) Change in
 LB.randomAssignment(List<ServerName> servers) API
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
X-Virus-Checked: Checked by ClamAV on apache.org


     [ https://issues.apache.org/jira/browse/HBASE-5510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ramkrishna.s.vasudevan reassigned HBASE-5510:
---------------------------------------------

    Assignee: ramkrishna.s.vasudevan
    
> Change in LB.randomAssignment(List<ServerName> servers) API
> -----------------------------------------------------------
>
>                 Key: HBASE-5510
>                 URL: https://issues.apache.org/jira/browse/HBASE-5510
>             Project: HBase
>          Issue Type: Improvement
>    Affects Versions: 0.92.0
>            Reporter: Anoop Sam John
>            Assignee: ramkrishna.s.vasudevan
>
>  In LB there is randomAssignment(List<ServerName servers>) API which will be used by AM to assign
>  a region from a down RS. [This will be also used in other cases like call to assign() API from client]
>  I feel it would be better to pass the HRegionInfo also into this method. When the LB making a choice for a region
>  assignment, when one RS is down, it would be nice that the LB knows for which region it is doing this server selection.
> +Scenario+
>  While one RS down, we wanted the regions to get moved to other RSs but a set of regions stay together. We are having custom load balancer but with the current way of LB interface this is not possible. Another way is I can allow a random assignment of the regions at the RS down time. Later with a cluster balance I can balance the regions as I need. But this might make regions assign 1st to one RS and then again move to another. Also for some time period my business use case can not get satisfied.
> Also I have seen some issue in JIRA which speaks about making sure that Root and META regions always sit in some specific RSs. With the current LB API this wont be possible in future.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira