Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Message-ID: <21062504.217031284596673449.JavaMail.jira@thor>
Date: Wed, 15 Sep 2010 20:24:33 -0400 (EDT)
From: "Andrew Ryan (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Subject: [jira] Commented: (HBASE-2991) Add support for refreshNodes in
 master
In-Reply-To: <6063216.166651284418172977.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Andrew Ryan commented on HBASE-2991:
------------------------------------

@matthew: I'm not sure I understand your comment about an includes list being unnecessary. They are part of both HDFS and Mapreduce and are very important. If one is moving nodes between clusters, includes/excludes lists become essential to insure that only the nodes we expect to be in the cluster are part of the cluster.

@stack: The HDFS and Mapreduce exclusions work slightly differently today, because in the HDFS case there is a "decommissioning" state that happens once the exclude command is received. But basically the desired behavior for the regionserver would be either:
1) Immediately shut down when excluded, or
2) Stay running, and periodically check to see if we are now un-excluded.

> Add support for refreshNodes in master
> --------------------------------------
>
>                 Key: HBASE-2991
>                 URL: https://issues.apache.org/jira/browse/HBASE-2991
>             Project: HBase
>          Issue Type: Wish
>          Components: master
>            Reporter: Matthew Welty
>            Priority: Minor
>
> -refreshNodes capabilities should be added to bin/hbase (or to a new script called `hbaseadmin`, if we want to maintain command name consistency) with cluster exclusion functionality similar to the capabilities of dfsadmin and mradmin. For ease of administration, the behavior of this option should be procedurally identical to the functions of the Hadoop Common components, including modifying the exclusion list via a local 'excludes' configuration file and display of excluded nodes via the web UI.
> A command overview for the behavior of -refreshNodes in dfsadmin is here:
> http://hadoop.apache.org/common/docs/current/commands_manual.html#dfsadmin
> The command overview for -refreshNodes in mradmin is here:
> http://hadoop.apache.org/common/docs/current/commands_manual.html#mradmin

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.