Return-Path: Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Received: (qmail 16379 invoked from network); 29 Jun 2010 21:07:46 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 29 Jun 2010 21:07:46 -0000 Received: (qmail 4366 invoked by uid 500); 29 Jun 2010 21:07:45 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 4331 invoked by uid 500); 29 Jun 2010 21:07:45 -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 4323 invoked by uid 99); 29 Jun 2010 21:07:45 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 Jun 2010 21:07:45 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 Jun 2010 21:07:42 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o5TKxpe1005856 for ; Tue, 29 Jun 2010 20:59:51 GMT Message-ID: <28898717.122851277845191361.JavaMail.jira@thor> Date: Tue, 29 Jun 2010 16:59:51 -0400 (EDT) From: "Allen Wittenauer (JIRA)" To: hdfs-issues@hadoop.apache.org Subject: [jira] Commented: (HDFS-1271) Decommissioning nodes not persisted between NameNode restarts In-Reply-To: <13028880.80081277660750144.JavaMail.jira@thor> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HDFS-1271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12883700#action_12883700 ] Allen Wittenauer commented on HDFS-1271: ---------------------------------------- +1. I've just been too lazy to file a bug. :) > Decommissioning nodes not persisted between NameNode restarts > ------------------------------------------------------------- > > Key: HDFS-1271 > URL: https://issues.apache.org/jira/browse/HDFS-1271 > Project: Hadoop HDFS > Issue Type: Bug > Components: name-node > Reporter: Travis Crawford > > Datanodes in the process of being decomissioned should still be decomissioning after namenode restarts. Currently they are marked as dead after a restart. > Details: > Nodes can be safely removed from a cluster by marking them as decomissioned and waiting for their data to be replicated elsewhere. This is accomplished by adding a node to the filed referenced by dfs.hosts.excluded, then refreshing nodes. > Decomissioning means block reports from the decomissioned datanode are no longer accepted by the namenode, meaning for decomissioning to occur the NN must have an existing block report. That is, a datanode can transition from: live --> decomissioning --> dead. Nodes can NOT transition from: dead --> decomissioning --> dead. > Operationally this is problematic because intervention is required should the NN restart while nodes are decomissioning, meaning in-house administration tools must be more complex, or more likely admins have to babysit the decomissioning process. > Someone more familiar with the code might have a better idea, but perhaps the first block report for dfs.hosts.excluded hosts should be accepted? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.