It appears I do not have any nodes with the Failover Controller role.  The screenshot below shows the hdfs instances filtered by that role.       ... View more

I do not know how to check if the "Failover Controller daemon running on the remaining NameNode".   Can you please tell me how to check? ... View more

  Thank you for your response.   I followed you advice below but I am getting the error below.  This is the same error as when I try a plain 'hdfs dfs -ls' command.     root@ip-10-0-0-154:/home/ubuntu/backup/data1# grep -B 1 -A 2 nameservices /var/run/cloudera-scm-agent/process/9908-hdfs-NAMENODE/hdfs-site.xml <property> <name>dfs.nameservices</name> <value>nameservice1</value> </property> ubuntu@ip-10-0-0-154:~/backup/data1$ hdfs dfs -ls hdfs://nameservice1/ 17/11/08 04:29:50 WARN retry.RetryInvocationHandler: Exception while invoking getFileInfo of class ClientNamenodeProtocolTranslatorPB after 1 fail over attempts. Trying to fail over after sleeping for 796ms.   Also, I should mention that when I go to CM, it shows that my one good namenode is in 'standby'.   Would it help to try a command like this?   ./hdfs haadmin -transitionToActive <nodename>   A second thing is that CM shows Automatic Failover is not enabled but there is a link to 'Enable' (see screenshot).  Maybe this is another option to help the standby node get promoted to active?   ... View more