Jerry He created HDFS-6001:
------------------------------
Summary: In HDFS HA setup, FileSystem.getUri returns
hdfs://<dfs.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-value-of-dfs.nameservices>
Here dfs.nameservices is defined when HA is enabled. In documentation:
{quote}
dfs.nameservices - the logical name for this new nameserviceChoose a logical
name for this nameservice, for example "mycluster", and use this logical name
for the value of this config option. The name you choose is arbitrary. It will
be used both for configuration and as the authority component of absolute HDFS
paths in the cluster.
Note: If you are also using HDFS Federation, this configuration setting 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', which
is not a valid host anywhere.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
