Troubleshooting
Problem
After a system disk failure the following steps to restore namenode were executed: After repair t he assumption is that after a system disk failure, $BIGINSIGHTS_HOME & $BIGINSIGHTS_VAR no longer exist nor does the /hadoop/hdfs/name/. - copy $BIGINSIGHTS_HOME & $BIGINSIGHTS_VAR from other NN - copy hadoop name directory from other NN - run syncconf.sh - stop.sh/start.sh hadoop
Symptom
2016-09-15 22:57:53,108 WARN org.apache.hadoop.hdfs.server.common.Storage: Cannot access storage directory /hadoop1/hadoop/hdfs/name
2016-09-15 22:57:53,111 INFO org.mortbay.log: Stopped SelectChannelConnector@pahmlbdnn01.local:50070
2016-09-15 22:57:53,212 INFO org.apache.hadoop.metrics2.impl.MetricsSystemImpl: Stopping NameNode metrics system...
2016-09-15 22:57:53,212 INFO org.apache.hadoop.metrics2.impl.MetricsSystemImpl: NameNode metrics system stopped.
2016-09-15 22:57:53,213 INFO org.apache.hadoop.metrics2.impl.MetricsSystemImpl: NameNode metrics system shutdown complete.
2016-09-15 22:57:53,214 FATAL org.apache.hadoop.hdfs.server.namenode.NameNode: Exception in namenode join java.io.IOException: Cannot start an HA namenode with name dirs that need recovery. Dir: Storage Directory /hadoop1/hadoop/hdfs/name state:
NON_EXISTENT
at org.apache.hadoop.hdfs.server.namenode.FSImage.
recoverStorageDirs(FSImage.java:285)
Log InLog in to view more of this document
Was this topic helpful?
Document Information
Modified date:
18 July 2020
UID
swg21990753