[ https://issues.apache.org/jira/browse/HDFS-13433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arpit Agarwal updated HDFS-13433: --------------------------------- Status: Patch Available (was: Open) v1 patch adds handling for federation cases. The setClientNamenodeAddress method was moved to a separate class NameNodeUtils#getClientNamenodeAddress. This method javadocs describe the logic for all the config combinations. > 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 > Attachments: HDFS-13433.01.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: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org