Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Message-ID: <30501495.226541292889423374.JavaMail.jira@thor>
Date: Mon, 20 Dec 2010 18:57:03 -0500 (EST)
From: "Suresh Srinivas (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Subject: [jira] Commented: (HDFS-1547) Improve decommission mechanism
In-Reply-To: <662967.224821292884142120.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HDFS-1547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12973422#action_12973422 ] 

Suresh Srinivas commented on HDFS-1547:
---------------------------------------

The way the files are named is confusing. With names such as include and exclude, one would think they are mutually exclusive.

include file is a list of datanodes in the cluster. Some of the nodes that have problems (access over ssh is not possible) etc. are excluded from by adding it to exclude list. See HADOOP-442 for details. Naming include file to another name, say datanodes and not the opposite of exclude would have reduced confusion.

> Improve decommission mechanism
> ------------------------------
>
>                 Key: HDFS-1547
>                 URL: https://issues.apache.org/jira/browse/HDFS-1547
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: name-node
>    Affects Versions: 0.23.0
>            Reporter: Suresh Srinivas
>            Assignee: Suresh Srinivas
>             Fix For: 0.23.0
>
>
> Current decommission mechanism driven using exclude file has several issues. This bug proposes some changes in the mechanism for better manageability. See the proposal in the next comment for more details.

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