As noted in the previous reply, I did not have any nodes with the Failover Controller role.  Importantly, I also had not enabled Automatic Failover despite running in an HA configuration.   I went ahead and added the Failover Controller role to both namenodes - the good one and the bad one.   After that, I attempted enable the Automatic Failover .  To do that, however, I needed to first start Zookeeper.     At that point, If I recall correctly, the other namenode was still not active but I then restarted the entire cluster and the automatic failover kicked in, using the other namenode as the active one and leaving the bad namenode in a stopped state. ... View more