Affects Version/s: 2.7.1, 3.0.0
Fix Version/s: None
my cluster has multiple namenodes using HDFS Federation.
webhdfs that is not defaultFS does not work properly.
when I uploaded to non defaultFS namenode using webhdfs.
uploaded file was founded at defaultFS namenode.
I think root cause is that
clientNamenodeAddress of non defaultFS namenode is always fs.defaultFS.
so webhdfs is redirected to datanode having wrong namenoderpcaddress parameter
finally file was located namenode of fs,defaultFS
configure fs.defaultFS of each namenode to its own nameservice.
hdfs://ns1 has fs.defaultFS=hdfs://ns1
hdfs://ns2 has fs.defaultFS=hdfs://ns2