[
https://issues.apache.org/jira/browse/HDFS-5122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arpit Gupta updated HDFS-5122:
------------------------------
Description:
For example if the dfs.nameservices is set to arpit
{code}
hdfs dfs -ls webhdfs://arpit:50070/tmp
or
hdfs dfs -ls webhdfs://arpit/tmp
{code}
does not work
You have to provide the exact active namenode hostname. On an HA cluster using
dfs client one should not need to provide the active nn hostname
was:
For example if the dfs.nameservices is set to arpit
{code}
hdfs dfs -ls webhdfs://arpit:50070/tmp
or
hdfs dfs -ls webhdfs://arpit/tmp
{code}
does not work
You have to provide the exact active namenode hostname
> webhdfs paths on an ha cluster still require the use of the active nn address
> rather than using the nameservice
> ---------------------------------------------------------------------------------------------------------------
>
> Key: HDFS-5122
> URL: https://issues.apache.org/jira/browse/HDFS-5122
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: ha
> Affects Versions: 2.1.0-beta
> Reporter: Arpit Gupta
>
> For example if the dfs.nameservices is set to arpit
> {code}
> hdfs dfs -ls webhdfs://arpit:50070/tmp
> or
> hdfs dfs -ls webhdfs://arpit/tmp
> {code}
> does not work
> You have to provide the exact active namenode hostname. On an HA cluster
> using dfs client one should not need to provide the active nn hostname
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
