Return-Path: X-Original-To: apmail-hadoop-hdfs-dev-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 767449305 for ; Tue, 3 Jul 2012 12:45:23 +0000 (UTC) Received: (qmail 75701 invoked by uid 500); 3 Jul 2012 12:45:22 -0000 Delivered-To: apmail-hadoop-hdfs-dev-archive@hadoop.apache.org Received: (qmail 75329 invoked by uid 500); 3 Jul 2012 12:45:21 -0000 Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-dev@hadoop.apache.org Delivered-To: mailing list hdfs-dev@hadoop.apache.org Received: (qmail 74657 invoked by uid 99); 3 Jul 2012 12:45:21 -0000 Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Jul 2012 12:45:21 +0000 Received: from isssues-vm.apache.org (localhost [127.0.0.1]) by issues-vm (Postfix) with ESMTP id 040BE142852 for ; Tue, 3 Jul 2012 12:45:21 +0000 (UTC) Date: Tue, 3 Jul 2012 12:45:21 +0000 (UTC) From: "Harsh J (JIRA)" To: hdfs-dev@hadoop.apache.org Message-ID: <1285741462.42.1341319521019.JavaMail.jiratomcat@issues-vm> Subject: [jira] [Resolved] (HDFS-1125) Removing a datanode (failed or decommissioned) should not require a namenode restart 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-1125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved HDFS-1125. --------------------------- Resolution: Duplicate Resolved via HDFS-1773. It was in the version after the one Allen tried above I think, thats why he may not have seen it? Please reopen if not. > Removing a datanode (failed or decommissioned) should not require a namenode restart > ------------------------------------------------------------------------------------ > > Key: HDFS-1125 > URL: https://issues.apache.org/jira/browse/HDFS-1125 > Project: Hadoop HDFS > Issue Type: Improvement > Components: name-node > Affects Versions: 0.20.2 > Reporter: Alex Loddengaard > Priority: Blocker > > I've heard of several Hadoop users using dfsadmin -report to monitor the number of dead nodes, and alert if that number is not 0. This mechanism tends to work pretty well, except when a node is decommissioned or fails, because then the namenode requires a restart for said node to be entirely removed from HDFS. More details here: > http://markmail.org/search/?q=decommissioned%20node%20showing%20up%20ad%20dead%20node%20in%20web%20based%09interface%20to%20namenode#query:decommissioned%20node%20showing%20up%20ad%20dead%20node%20in%20web%20based%09interface%20to%20namenode+page:1+mid:7gwqwdkobgfuszb4+state:results > Removal from the exclude file and a refresh should get rid of the dead node. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira