Return-Path: X-Original-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C30A62257 for ; Tue, 3 May 2011 22:21:42 +0000 (UTC) Received: (qmail 3947 invoked by uid 500); 3 May 2011 22:21:42 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 3917 invoked by uid 500); 3 May 2011 22:21:42 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-issues@hadoop.apache.org Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 3909 invoked by uid 99); 3 May 2011 22:21:42 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 May 2011 22:21:42 +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, 03 May 2011 22:21:41 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id 6D897C0FF1 for ; Tue, 3 May 2011 22:21:03 +0000 (UTC) Date: Tue, 3 May 2011 22:21:03 +0000 (UTC) From: "Tsz Wo (Nicholas), SZE (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: <1305729015.19963.1304461263445.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <1935204847.2654.1300746305906.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Updated] (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 X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HDFS-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo (Nicholas), SZE updated HDFS-1773: ----------------------------------------- Component/s: name-node > 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 > Components: name-node > Affects Versions: 0.20.203.1, 0.23.0 > Environment: branch-20-security and trunk. > Reporter: Tanping Wang > Assignee: Tanping Wang > Priority: Minor > Fix For: 0.20.204.0, 0.23.0 > > Attachments: HDFS-1773-2.patch, HDFS-1773-3.patch, HDFS-1773.patch, HDFS-1867.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