when we start the namenode in ambari cluster we get the following errors inspite the resolving of the hosts/ips are ok what else chould be hdfs namenode -bootstrapStandby -force 17/12/05 07:23:15 FATAL ha.BootstrapStandby: Unable to fetch namespace information from active NN at master01.sys784.com/110.14.28.153:8020: Call From master03.sys784.co m/110.14.27.162 to master01.sys784.com:8020 failed on connection exception: java.net.ConnectException: Connection refused; For more details see: http://wiki.apache.org/ha doop/ConnectionRefused ... View more

in our ambari cluster we see the following on the first nn1 $ hdfs haadmin -checkHealth master01 Illegal argument: Unable to determine service address for namenode 'master01' on the second namenode $ hdfs haadmin -checkHealth master03 Illegal argument: Unable to determine service address for namenode 'master03' what could be the problem here ? and how to debug the command in order to verify what is the root cause ? remark - DNS configuration on all hosts/IP are right other example since namenode is down [hdfs@master01 root]$ hdfs haadmin -transitionToActive --forceactive master01 Illegal argument: Unable to determine service address for namenode 'master01' ... View more