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 5193D17CAB for ; Tue, 22 Sep 2015 19:04:14 +0000 (UTC) Received: (qmail 96227 invoked by uid 500); 22 Sep 2015 19:04:04 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 96159 invoked by uid 500); 22 Sep 2015 19:04:04 -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 96043 invoked by uid 99); 22 Sep 2015 19:04:04 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Sep 2015 19:04:04 +0000 Date: Tue, 22 Sep 2015 19:04:04 +0000 (UTC) From: "Anu Engineer (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HDFS-9109) dfs.datanode.dns.interface does not work with hosts file based setups 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-9109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14903232#comment-14903232 ] Anu Engineer commented on HDFS-9109: ------------------------------------ +1 (non-binding) Had some minor nitpicks : # In the DNS.java, we now have both java.net.InetAddress and com.google.common.net.InetAddresses. Hence you might want to consider renaming getIPsAsInetAddresses as something line getIPsAsInetAddressList since you are returning the one from java namespace-- same for the comments or you can stop using that guava class for IP Address verification. # As for testing I was wondering if we might be able to leverage sun.net.spi.nameservice.NameService and provide our own DNS lookup service ? we do have to set the java system variables before the test gets run though. But as you said it might be something that we can consider for future. > dfs.datanode.dns.interface does not work with hosts file based setups > --------------------------------------------------------------------- > > Key: HDFS-9109 > URL: https://issues.apache.org/jira/browse/HDFS-9109 > Project: Hadoop HDFS > Issue Type: Bug > Components: datanode > Reporter: Arpit Agarwal > Assignee: Arpit Agarwal > Attachments: HDFS-9109.01.patch, HDFS-9109.02.patch, HDFS-9109.03.patch > > > The configuration setting {{dfs.datanode.dns.interface}} lets the DataNode select its hostname by doing a reverse lookup of IP addresses on the specific network interface. This does not work {{when /etc/hosts}} is used to setup alternate hostnames, since {{DNS#reverseDns}} only queries the DNS servers. -- This message was sent by Atlassian JIRA (v6.3.4#6332)