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 E61406DB0 for ; Tue, 24 May 2011 03:06:35 +0000 (UTC) Received: (qmail 59080 invoked by uid 500); 24 May 2011 03:06:35 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 58958 invoked by uid 500); 24 May 2011 03:06:34 -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 58949 invoked by uid 99); 24 May 2011 03:06:31 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 May 2011 03:06:31 +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; Tue, 24 May 2011 03:06:30 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id 46031DA7B4 for ; Tue, 24 May 2011 03:05:50 +0000 (UTC) Date: Tue, 24 May 2011 03:05:50 +0000 (UTC) From: "Vishal Kathuria (JIRA)" To: issues@hbase.apache.org Message-ID: <2139833516.38249.1306206350283.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <2068261008.13338.1304142843122.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (HBASE-3833) ability to support includes/excludes list in Hbase 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-3833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13038364#comment-13038364 ] Vishal Kathuria commented on HBASE-3833: ---------------------------------------- Stack: My intention was build a graceful shutdown (that is the reason I assign the regions first and then expire the server). I assumed that assign* API unloads them off the source region server when assigning them to the new region server, but I guess I was wrong in that assumption. Let me take a look at the code again to see how I can change it to make the shutdown graceful and not have the situation you mentioned of two servers owning the region - that is clearly not desirable. Yuzhi: In case any of the meta regions are involved, then the MetaServerShutdownHandler is dispatched. That class has both isCarryingRoot() and isCarryingMeta() defined. I will publish another patch in a couple of days. Stack, please hold on to hacking this in. Thanks! Vishal > ability to support includes/excludes list in Hbase > -------------------------------------------------- > > Key: HBASE-3833 > URL: https://issues.apache.org/jira/browse/HBASE-3833 > Project: HBase > Issue Type: Improvement > Components: client, regionserver > Affects Versions: 0.90.2 > Reporter: dhruba borthakur > Assignee: dhruba borthakur > Attachments: excl-patch.txt, excl-patch.txt > > > An HBase cluster currently does not have the ability to specify that the master should accept regionservers only from a specified list. This helps preventing administrative errors where the same machine could be included in two clusters. It also allows the administrator to easily remove un-ssh-able machines from the cluster. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira