[ 
https://issues.apache.org/jira/browse/HDFS-13433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arpit Agarwal updated HDFS-13433:
---------------------------------
    Description: 
In the following HA+Federated setup:
# NS1 -> namenodes nn1, nn2
# NS2 -> namenodes nn3, nn4
# fs.defaultFS is {{hdfs://ns1}}.

A webhdfs request issued to nn3 will be routed to NS1. This is because 
{{setClientNamenodeAddress}} initializes {{NameNode#clientNamenodeAddress}} 
using fs.defaultFS before the config is overriden.

  was:
In the following HA+Federated setup:
# NS1 -> namenodes nn1, nn2
# NS2 -> namenodes nn3, nn4
# fs.defaultFS is {{hdfs://ns1}}.

A webhdfs request issued to nn3 will be routed to nn1. This is because 
{{setClientNamenodeAddress}} initializes {{NameNode#clientNamenodeAddress}} 
using fs.defaultFS before the config is overriden.


> webhdfs requests can be routed incorrectly in federated cluster
> ---------------------------------------------------------------
>
>                 Key: HDFS-13433
>                 URL: https://issues.apache.org/jira/browse/HDFS-13433
>             Project: Hadoop HDFS
>          Issue Type: Bug
>            Reporter: Arpit Agarwal
>            Assignee: Arpit Agarwal
>            Priority: Critical
>
> In the following HA+Federated setup:
> # NS1 -> namenodes nn1, nn2
> # NS2 -> namenodes nn3, nn4
> # fs.defaultFS is {{hdfs://ns1}}.
> A webhdfs request issued to nn3 will be routed to NS1. This is because 
> {{setClientNamenodeAddress}} initializes {{NameNode#clientNamenodeAddress}} 
> using fs.defaultFS before the config is overriden.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org

Reply via email to