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 654781042D for ; Mon, 8 Jul 2013 00:23:48 +0000 (UTC) Received: (qmail 45315 invoked by uid 500); 8 Jul 2013 00:23:48 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 45283 invoked by uid 500); 8 Jul 2013 00:23:48 -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 45274 invoked by uid 99); 8 Jul 2013 00:23:48 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Jul 2013 00:23:48 +0000 Date: Mon, 8 Jul 2013 00:23:48 +0000 (UTC) From: "Zesheng Wu (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HDFS-4959) Decommission data nodes, There is no response 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-4959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13701710#comment-13701710 ] Zesheng Wu commented on HDFS-4959: ---------------------------------- A simple fix may look like this, but this is not a good fix: {code} public void refreshNodes() throws IOException { namesystem.refreshNodes(); namesystem.checkOperation(OperationCategory.WRITE); } {code} > Decommission data nodes, There is no response > --------------------------------------------- > > Key: HDFS-4959 > URL: https://issues.apache.org/jira/browse/HDFS-4959 > Project: Hadoop HDFS > Issue Type: Bug > Components: ha, hdfs-client, namenode > Affects Versions: 2.0.5-alpha > Reporter: Fengdong Yu > > There is "dfs.hosts.exclude" configured before NN start. Active/Standby works well. > 1)Add two datanodes IPAddr to the exclude file on the both Active and Standby NN. > 2)run: hdfs dfsadmin -refreshNodes on the Active NN, but there isn't any logs in the ActiveNN log. but decommission logs showed in the StandbyNN log. > There is no decommission datanodes showed on the Active NN webUI. but there does have decommission datanodes showed on the Standby NN webUI. > But the decommission process is very very slow, it indicates it cannot finish forever. > I do think this is a bug. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira