Return-Path: 
 <hdfs-issues-return-48959-apmail-hadoop-hdfs-issues-archive=hadoop.apache.org@hadoop.apache.org>
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 D413AD649
	for <apmail-hadoop-hdfs-issues-archive@minotaur.apache.org>;
 Thu, 13 Sep 2012 17:38:08 +0000 (UTC)
Received: (qmail 56570 invoked by uid 500); 13 Sep 2012 17:38:08 -0000
Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org
Received: (qmail 56454 invoked by uid 500); 13 Sep 2012 17:38:07 -0000
Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:hdfs-issues-help@hadoop.apache.org>
List-Unsubscribe: <mailto:hdfs-issues-unsubscribe@hadoop.apache.org>
List-Post: <mailto:hdfs-issues@hadoop.apache.org>
List-Id: <hdfs-issues.hadoop.apache.org>
Reply-To: hdfs-issues@hadoop.apache.org
Delivered-To: mailing list hdfs-issues@hadoop.apache.org
Received: (qmail 56420 invoked by uid 99); 13 Sep 2012 17:38:07 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Sep 2012 17:38:07 +0000
Date: Fri, 14 Sep 2012 04:38:07 +1100 (NCT)
From: "Andy Isaacson (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <614255216.75768.1347557887841.JavaMail.jiratomcat@arcas>
Subject: [jira] [Created] (HDFS-3934) duplicative dfs_hosts entries handled
 wrong
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394

Andy Isaacson created HDFS-3934:
-----------------------------------

             Summary: duplicative dfs_hosts entries handled wrong
                 Key: HDFS-3934
                 URL: https://issues.apache.org/jira/browse/HDFS-3934
             Project: Hadoop HDFS
          Issue Type: Bug
    Affects Versions: 2.0.1-alpha
            Reporter: Andy Isaacson
            Assignee: Andy Isaacson
            Priority: Minor


A dead DN listed in dfs_hosts_allow.txt by IP and in dfs_hosts_exclude.txt by hostname ends up being displayed twice in {{dfsnodelist.jsp?whatNodes=DEAD}} after the NN restarts because {{getDatanodeListForReport}} does not handle such a "pseudo-duplicate" correctly:
# the "Remove any nodes we know about from the map" loop no longer has the knowledge to remove the spurious entries
# the "The remaining nodes are ones that are referenced by the hosts files" loop does not do hostname lookups, so does not know that the IP and hostname refer to the same host.

Relatedly, such an IP-based dfs_hosts entry results in a cosmetic problem in the JSP output:  The *Node* column shows ":50010" as the nodename, with HTML markup {{<a href="http://:50075/browseDirectory.jsp?namenodeInfoPort=50070&amp;dir=%2F&amp;nnaddr=172.29.97.196:8020" title="172.29.97.216:50010">:50010</a>}}.

--
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