Thanks for the alternatives Wes Floyd, It works one way again. WEB HDFS : Yes WEBHDFS works from cluster A again. From Cluster B we use a numeric UserID because of which webhdfs call is failing, I see a patch for this anyways https://issues.apache.org/jira/browse/HDFS-4983. Is this patch not available as part HDP 2.4 ! Other cases: We tried to add -fs option same result Most weird part is hadoop fs -ls hdfs://a.a.a.a:8020, it still not throwing error it still gives the values of the cluster B. Extra Cluster Info: Cluster B has WanDisco installed, is this setup causing any issue. I hope we use WanDisco fusion client Jar instead of the hadoop Jars at the backend. Any pointers here! core_site.xml Entries: <property>
<name>fs.hdfs.impl</name>
<value>com.wandisco.fs.client.FusionHdfs</value>
</property> <property>
<name>fusion.handshakeToken.dir</name>
<value>##SOME DIR##</value>
</property> <property>
<name>fusion.ihc.http.policy</name>
<value>HTTP_ONLY</value>
</property> <property>
<name>fusion.ihc.ssl.enabled</name>
<value>true</value>
</property>
... View more
