Report the following error
Workaround:
Method One: (results do not work)
Through shell command, Hadoop/bin/hdfs haadmin-failover--forceactive hadoop2 HADOOP1 (Note that this method was originally forced to switch namenode in manual recovery)
Returns results, unsupported, and sincere hints that this command will only work in the case of a manual failover
Method Two: (works)
I used JPS check the status of the zookeeper cluster, found that no indication of the failure of two, the original is the reason for ZK, then restarted the ZK cluster, and then restarted Zkfailovercontroller, no such role exists, Naturally, it doesn't automatically switch namenode.
If you think reading this blog gives you something to gain, you might want to click " recommend " in the lower right corner.
If you want to find my new blog more easily, click on " Follow me " in the lower left corner.
If you are interested in what my blog is talking about, please keep following my follow-up blog, I am " Liu Chao ★ljc".
This article is copyright to the author and the blog Park, Welcome to reprint, but without the consent of the author must retain this paragraph, and in the article page obvious location to the original link, otherwise reserves the right to pursue legal responsibility.
Hadoop Error Operation category READ is not supported in state standby