[ https://issues.apache.org/jira/browse/HDFS-5122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13763665#comment-13763665 ]
Philip Zeyliger commented on HDFS-5122: --------------------------------------- Haohui, Your patch doesn't seem to handle the possibility that the first namenode isn't the currently active one. So it's not just not handling failover during the lifetime of the client, but it's not handling a case where the configuration happens to have the currently active namenode first. It seems like the code ought to at least try to access (with a timeout) the namenode to see if it's active, no? > WebHDFS should support logical service names in URIs > ---------------------------------------------------- > > Key: HDFS-5122 > URL: https://issues.apache.org/jira/browse/HDFS-5122 > Project: Hadoop HDFS > Issue Type: Bug > Components: ha, webhdfs > Affects Versions: 2.1.0-beta > Reporter: Arpit Gupta > Assignee: Haohui Mai > Attachments: HDFS-5122.patch > > > 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