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 2A819108C4 for ; Tue, 6 Jan 2015 16:42:35 +0000 (UTC) Received: (qmail 78758 invoked by uid 500); 6 Jan 2015 16:42:36 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 78702 invoked by uid 500); 6 Jan 2015 16:42:36 -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 78689 invoked by uid 99); 6 Jan 2015 16:42:35 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Jan 2015 16:42:35 +0000 Date: Tue, 6 Jan 2015 16:42:35 +0000 (UTC) From: "Benoit Perroud (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HDFS-7586) HFTP does not work when namenode bind on wildcard 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-7586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14266360#comment-14266360 ] Benoit Perroud commented on HDFS-7586: -------------------------------------- Thanks for the pointer. You're right in >=2.5.0. In <2.5, the way to do was setting 0.0.0.0:8020, which leads to the issue described here. And has the multihoming been tested with HFTP too? > HFTP does not work when namenode bind on wildcard > ------------------------------------------------- > > Key: HDFS-7586 > URL: https://issues.apache.org/jira/browse/HDFS-7586 > Project: Hadoop HDFS > Issue Type: Bug > Components: datanode > Affects Versions: 2.2.0, 2.3.0, 2.4.0 > Reporter: Benoit Perroud > Priority: Minor > Attachments: HDFS-7586-v0.1.txt > > > When wildcard binding for NameNode RPC is turned on (i.e. dfs.namenode.rpc-address=0.0.0.0:8020), HFTP download is failing. > Call to http://namenode:50070/data/.. returns the header Location with parameter nnaddr=0.0.0.0:8020, which is unlikely to ever succeed :) > The idea would be, if wildcard binding is enabled, to get read the IP address the request is actually connected to from the HttpServletRequest and return this one. > WDYT? > How to reproduce: > 1. Turn on wildcard binding > {code}dfs.namenode.rpc-address=0.0.0.0:8020{code} > 2. Upload a file > {code}$ echo "123" | hdfs dfs -put - /tmp/randomFile.txt{code} > 3. Validate it's failing > {code} > $ hdfs dfs -cat hftp://namenode1/tmp/randomFile.txt > {code} > 4. Get more details via curl > {code} > $ curl -vv http://namenode1:50070/data/tmp/randomFile.txt?ugi=hdfs | grep "Location:" > Location: http://datanode003:50075/streamFile/tmp/randomFile.txt?ugi=hdfs&nnaddr=0.0.0.0:8020 > {code} > We can clearly see the 0.0.0.0 returned as the NN ip. -- This message was sent by Atlassian JIRA (v6.3.4#6332)