[
https://issues.apache.org/jira/browse/HDFS-13433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16459694#comment-16459694
]
Kihwal Lee commented on HDFS-13433:
-----------------------------------
This breaks the IP failover HA setup.
In your example, nn3/nn4 start up with a config containing defaultFS set to
ns1? I would say that is a misconfig. Isn't it supposed to be hdfs://ns2 for
nn3/nn4?
> 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
> Components: webhdfs
> Reporter: Arpit Agarwal
> Assignee: Arpit Agarwal
> Priority: Critical
> Fix For: 3.1.1, 3.0.3
>
> Attachments: HDFS-13433.01.patch, HDFS-13433.02.patch,
> HDFS-13433.03.patch, HDFS-13433.04.patch
>
>
> In the following HA+Federated setup with two nameservices ns1 and ns2:
> # ns1 -> namenodes nn1, nn2
> # ns2 -> namenodes nn3, nn4
> # fs.defaultFS is {{hdfs://ns1}}.
> A webhdfs request issued to nn3/nn4 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: [email protected]
For additional commands, e-mail: [email protected]
