Reasons why the NameNode fails to start and solutions
Problem: After starting Hadoop, I checked with JPS and found no NameNode
The NAMenode Format creates a new NAMenodeld every time, and TMP/DFS /data contains the ID under the last format. The Namenode Format clears the data under the Namenode, but does not clean the data under the Datanode, which causes startup failure.
Solutions:
- stop running hadoop
stop -dfs.sh
- delete the file items mapped by hadoop.tmp.dir in the core-site configuration file, generally hadoop/ TMP folder
sudo rm -r tmp
- performs formatting
./bin/hdfs namenode -format
- restart
start-hdfs.sh
Read More:
- Hadoop datanode using JPS to view the solution that can’t be started
- Error in initializing namenode when configuring Hadoop!!!
- Error: attempting to operate on HDFS namenode as root
- Namenode startup error: outofmemoryerror: Java heap space
- Start Additional NameNode [How to Solve]
- This program cannot be started because the computer is missing COpenGL.dll
- Oracle reports an error and lsnrctl listening cannot be started
- The main class could not be found or loaded when springboot started
- Elasticsearch cluster cannot be started. The following prompt fails to send join request to master appears
- MAMP failed to start: Apache could’t be started. Please check your MAMP installation and configuration
- Systemctl command doesn’t exist. How to solve the problem that the service can’t be started
- Job for apache2.service failed apache2 cannot be started
- Error warning: mysqli_ error() expects parameter 1 to be mysqli, null given。 Any idea why?
- Apache service can’t be started under xampp, reporting port occupancy class error [error] Apache will not start without the configured ports free!
- CDH Namenode Abnormal stop Error: flush failed for required journal (JournalAndStream(mgr=QJM to
- [Solved] Appium Android, Appium settings and Unclock method will be installed every time the phone is started
- Apache2 cannot be started and an error is reported for apache2.service failed because the control process exited with error code.
- dfs.namenode.name . dir and dfs.datanode.data .dir dfs.name.dir And dfs.data.dir What do you mean
- The installation of docker desktop failed. After successful installation, the docker can not be started
- This program cannot be started because vcruntime140 is missing from your computer_ 1.dll。 Try to install the program again to solve the problem.