Steps to resolve when Datanode services is not starting

• Kiran Dalvi
• 05 Oct, 2021
• 0 Comments
• 46 Secs Read

Steps to resolve when Datanode services is not starting

Check the hadoop services status. Below datanode service is not running

1 2 3 4 5 6

hdoop@hadoop:~$ jps 2258 ResourceManager 1730 NameNode 2038 SecondaryNameNode 2391 NodeManager 2735 Jps

go to core-site.xml and check the path of tmp directory. We need to remove and create same directory

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19

hdoop@hadoop:~/hadoop-3.2.1/etc/hadoop$ pwd /home/hdoop/hadoop-3.2.1/etc/hadoop   <configuration>  <property>         <name>hadoop.tmp.dir</name>         <value>/home/hdoop/tmpdata</value>         <description>A base for other temporary directories.</description>     </property>     <property>         <name>fs.default.name</name>         <value>hdfs://127.0.0.1:9000</value>         <description>The name of the default file system></description>     </property> </configuration>   rm -rf /home/hdoop/tmpdata   mkdir -p /home/hdoop/tmpdata

open hdfs-site.xml and remove datanode and namenode directory

1 2 3 4 5 6 7

vi hdfs-site.xml   rm -rf /home/hdoop/dfsdata/namenode rm -rf /home/hdoop/dfsdata/datanode/   mkdir -p /home/hdoop/dfsdata/namenode mkdir -p /home/hdoop/dfsdata/datanode/

Format namenode and start all services. You will find datanode there

1 2 3 4 5 6 7 8 9 10 11

hadoop namenode -format   start-all.sh   hdoop@hadoop:~/hadoop-3.2.1/etc/hadoop$ jps 4064 SecondaryNameNode 3729 NameNode 4264 ResourceManager 3866 DataNode 4717 Jps 4398 NodeManager