Return-Path: 
 <hdfs-issues-return-79601-apmail-hadoop-hdfs-issues-archive=hadoop.apache.org@hadoop.apache.org>
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 8CC71100E8
	for <apmail-hadoop-hdfs-issues-archive@minotaur.apache.org>;
 Mon, 24 Feb 2014 05:48:34 +0000 (UTC)
Received: (qmail 14272 invoked by uid 500); 24 Feb 2014 05:48:26 -0000
Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org
Received: (qmail 13438 invoked by uid 500); 24 Feb 2014 05:48:21 -0000
Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:hdfs-issues-help@hadoop.apache.org>
List-Unsubscribe: <mailto:hdfs-issues-unsubscribe@hadoop.apache.org>
List-Post: <mailto:hdfs-issues@hadoop.apache.org>
List-Id: <hdfs-issues.hadoop.apache.org>
Reply-To: hdfs-issues@hadoop.apache.org
Delivered-To: mailing list hdfs-issues@hadoop.apache.org
Received: (qmail 13418 invoked by uid 99); 24 Feb 2014 05:48:19 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 24 Feb 2014 05:48:19 +0000
Date: Mon, 24 Feb 2014 05:48:19 +0000 (UTC)
From: "Jerry He (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12696847.1393220880157.90670.1393220899328@arcas>
In-Reply-To: <JIRA.12696847.1393220880157@arcas>
References: <JIRA.12696847.1393220880157@arcas>
Subject: [jira] [Created] (HDFS-6001) In HDFS HA setup, FileSystem.getUri
 returns hdfs://<dfs.nameservices>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394

Jerry He created HDFS-6001:
------------------------------

             Summary: In HDFS HA setup, FileSystem.getUri returns hdfs://<d=
fs.nameservices>
                 Key: HDFS-6001
                 URL: https://issues.apache.org/jira/browse/HDFS-6001
             Project: Hadoop HDFS
          Issue Type: Bug
          Components: ha
    Affects Versions: 2.2.0
            Reporter: Jerry He
            Priority: Minor


When hdfs is set up with HA enable, FileSystem.getUri returns hdfs://<the-v=
alue-of-dfs.nameservices>
Here dfs.nameservices is defined when HA is enabled. In documentation:
{quote}
dfs.nameservices=C2=A0- the logical name for this new nameserviceChoose a l=
ogical name for this nameservice, for example "mycluster", and use this log=
ical name for the value of this config option. The name you choose is arbit=
rary. It will be used both for configuration and as the authority component=
 of absolute HDFS paths in the cluster.
Note:=C2=A0If you are also using HDFS Federation, this configuration settin=
g should also include the list of other nameservices, HA or otherwise, as a=
 comma-separated list.
<property>
  <name>dfs.nameservices</name>
  <value>mycluster</value>
</property>
{quote}
This is probably ok or even intended.  But a caller may further process the=
 URI, for example, call URI.getHost(). This will return the 'mycluster', wh=
ich is not a valid host anywhere.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)