Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Mon, 2 May 2011 21:19:03 +0000 (UTC)
From: "Tanping Wang (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: 
 <354710015.16425.1304371143220.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1935204847.2654.1300746305906.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Reopened] (HDFS-1773) Remove a datanode from cluster if
 include list is not empty and this datanode is removed from both include
 and exclude lists
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Tanping Wang reopened HDFS-1773:
--------------------------------


Port this jira to trunk.  Mark HDFS-1867 as a duplication of this jira.

> Remove a datanode from cluster if include list is not empty and this datanode is removed from both include and exclude lists
> ----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HDFS-1773
>                 URL: https://issues.apache.org/jira/browse/HDFS-1773
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>    Affects Versions: 0.20.203.1
>         Environment: branch-20-security
>            Reporter: Tanping Wang
>            Assignee: Tanping Wang
>            Priority: Minor
>             Fix For: 0.20.204.0
>
>         Attachments: HDFS-1773-2.patch, HDFS-1773-3.patch, HDFS-1773.patch
>
>
> Our service engineering team who operates the clusters on a daily basis founds it is confusing that after a data node is decommissioned, there is no way to make the cluster forget about this data node and it always remains in the dead node list.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira