Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Tue, 30 Jun 2015 12:46:04 +0000 (UTC)
From: "Walter Su (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12841681.1435667926000.57661.1435668364699@Atlassian.JIRA>
In-Reply-To: <JIRA.12841681.1435667926000@Atlassian.JIRA>
References: <JIRA.12841681.1435667926000@Atlassian.JIRA>
 <JIRA.12841681.1435667926933@arcas>
Subject: [jira] [Updated] (HDFS-8700) favoredNodes should accept ip addr
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HDFS-8700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Walter Su updated HDFS-8700:
----------------------------
    Status: Patch Available  (was: Open)

> favoredNodes should accept ip addr
> ----------------------------------
>
>                 Key: HDFS-8700
>                 URL: https://issues.apache.org/jira/browse/HDFS-8700
>             Project: Hadoop HDFS
>          Issue Type: Bug
>            Reporter: Walter Su
>            Assignee: Walter Su
>            Priority: Minor
>         Attachments: HDFS-8700.01.patch
>
>
> NameNode accepts two forms of FavoredNodes, {{ip:port}} and {{host:port}}
> DFSClient#create(..) only uses {{host:port}}, if favoredNodes is created by 
> {code}
> new InetSocketAddress(ip, port)
> {code}
> DFSClient will attempt a reverse lookup locally to get {{host:port}}, instead of sending {{ip:port}} directly to NameNode.
> It's not a problem in production. But it's a problem in MiniDFSCluster.
> MiniDFSCluster use fake hostname "host1.foo.com" to start DataNodes.
> DFSClient doesn't use StaticMapping. So if DFSClient do reverse lookup, "127.0.0.1:50470" becomes "localhost:50470".


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)