I continued the resolution of this issue in another thread specific to the error:    ls: Operation category READ is not supported in state standby   The solution is marked on that thread, however, a quick summary was that I needed to add the Failover Controller role to a node in my cluster, enable Automatic Failover, and then restart the cluster for it all to kick in. ... View more

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 using the link shown in the screenshot from this post.  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