Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Thu, 23 Jun 2011 19:32:47 +0000 (UTC)
From: "Jitendra Nath Pandey (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: 
 <1825465964.34327.1308857567695.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <720621614.22666.1308606887605.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HDFS-2086) If the include hosts list contains
 host name, after restarting namenode, datanodes registrant is denied
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HDFS-2086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13054050#comment-13054050 ] 

Jitendra Nath Pandey commented on HDFS-2086:
--------------------------------------------

Patch looks good to me

nit: In checkInList, can we avoid repeating (iaddr != null)?

+1 otherwise. 

> If the include hosts list contains host name, after restarting namenode, datanodes registrant is denied 
> --------------------------------------------------------------------------------------------------------
>
>                 Key: HDFS-2086
>                 URL: https://issues.apache.org/jira/browse/HDFS-2086
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: name-node
>    Affects Versions: 0.23.0
>            Reporter: Tanping Wang
>            Assignee: Tanping Wang
>             Fix For: 0.23.0
>
>         Attachments: HDFS-2086.2.patch, HDFS-2086.3.patch, HDFS-2086.4.patch, HDFS-2086.5.patch, HDFS-2086.6.patch, HDFS-2086.patch
>
>
> As the title describes the problem:  if the include host list contains host name, after restarting namenodes, the datanodes registrant is denied by namenodes.  This is because after namenode is restarted, the still alive data node will try to register itself with the namenode and it identifies itself with its *IP address*.  However, namenode only allows all the hosts in its hosts list to registrant and all of them are hostnames. So namenode would deny the datanode registration.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira