https://community.cloudera.com/t5/Support-Questions/hdfs-client-takes-20s-to-failover-to-alternate-namenode/m-p/208692#M170649 <P>I have a cluster with two namenodes configured in a for HA. For failover testing, we purposely turned off namenode 1. However, when trying to check an HDFS file size from server 2, the HDFS client call still attempts to connect to namenode 1 first. This causes a 20s delay while it times out before it tries namenode2. I've tried setting the dfs.ha.namenodes.xxx property to change the search order but without success. It always trys namenode1 first and then, after 20s goes to namenode 2. This is causing unacceptable delays in our system which needs faster response times than having to wait 20s to connect to the correct namenode. Does anyone how I may rectify this problem?</P><P>Thanks, David</P> Fri, 06 Oct 2017 22:42:27 GMT kc7bfi 2017-10-06T22:42:27Z