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 E41CB60AF for ; Wed, 18 May 2011 23:47:28 +0000 (UTC) Received: (qmail 36338 invoked by uid 500); 18 May 2011 23:47:28 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 36205 invoked by uid 500); 18 May 2011 23:47:28 -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 36142 invoked by uid 99); 18 May 2011 23:47:28 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 May 2011 23:47:28 +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; Wed, 18 May 2011 23:47:27 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id 05387D0BAD for ; Wed, 18 May 2011 23:46:48 +0000 (UTC) Date: Wed, 18 May 2011 23:46:48 +0000 (UTC) From: "stack (JIRA)" To: issues@hbase.apache.org Message-ID: <24312988.24794.1305762408018.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=13035859#comment-13035859 ] stack commented on HBASE-3833: ------------------------------ bq. 2. enqueues a shutdownhandler to move all the regions off this node ServerShutdownHandler splits logs and reassigns regions that were (or *are* in the decommissioning case) up on the shutdown server. It does not unload them off the hosting regionserver. So, it looks to me as though regions can be in two places at once... still on the server that has been marked decommissioned and up in the new locations that ServerShutdownHandler has assigned them too. This looks a little dangerous (if I am reading this right). If decommissioning, it looks like you expire the server only at the end of the server shutdown processing (your call to markServerExpiry will be noticed by the hosting regionserver and it'll shut itself down closing out the regions it was hosting). New JIRA for Karthiks suggestion sounds good. > 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