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 E86EF6151 for ; Mon, 20 Jun 2011 21:59:10 +0000 (UTC) Received: (qmail 12010 invoked by uid 500); 20 Jun 2011 21:59:10 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 11967 invoked by uid 500); 20 Jun 2011 21:59:10 -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 11959 invoked by uid 99); 20 Jun 2011 21:59:10 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 20 Jun 2011 21:59:10 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED,T_RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 20 Jun 2011 21:59:08 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id 7D901424CB4 for ; Mon, 20 Jun 2011 21:58:47 +0000 (UTC) Date: Mon, 20 Jun 2011 21:58:47 +0000 (UTC) From: "Tanping Wang (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: <1151091345.22674.1308607127511.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 X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HDFS-2086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13052244#comment-13052244 ] Tanping Wang commented on HDFS-2086: ------------------------------------ There is a second part of this problem. When namenode checks datanode status by calling FSNameSystem#getDatanodeListForReport The namenode goes over its include hosts list and tries to determine if all the hosts in the include list are all registrant. If not, the host will be added into the dead list. In our case, as just mentioned early, after the namenode restarted, datanode registrants itself with its *IP address*. But the include list still contains its *host name*. So the hostname is not recognized by namenode and is added into the dead list when namenode reports the datanodes status. > 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 > Fix For: 0.23.0 > > > As the tile 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