Support Questions
Find answers, ask questions, and share your expertise

namdenode failed

namdenode failed

New Contributor

Hi ,

My hadoop version is The namenode running on my hadoop clulser was shut down. I checked the logs, and found the error message only in the secondary name logs:


2014-09-27 22:18:54,930 WARN org.apache.hadoop.hdfs.server.namenode.SecondaryNameNode: Checkpoint done. New Image Size: 29552383
2014-09-27 22:19:42,792 INFO org.mortbay.log:$SelectSet@8135daf JVM BUG(s) - injecting delay2 times
2014-09-27 22:19:42,792 INFO org.mortbay.log:$SelectSet@8135daf JVM BUG(s) - recreating selector 2 times, canceled keys 38 times
2014-09-27 23:18:55,508 INFO org.apache.hadoop.hdfs.server.namenode.FSNamesystem: Number of transactions: 0 Total time for transactions(ms): 0Number of transactions batched in Syncs: 0 Number of syncs: 0 SyncTimes(ms): 0
2014-09-27 23:18:55,508 FATAL org.apache.hadoop.hdfs.server.namenode.FSNamesystem: Fatal Error : All storage directories are inaccessible.
2014-09-27 23:18:55,509 INFO org.apache.hadoop.hdfs.server.namenode.SecondaryNameNode: SHUTDOWN_MSG:


There was anonther error message apprears in one of my datanodes:


2014-09-27 01:03:58,535 ERROR org.apache.hadoop.hdfs.server.datanode.DataNode: DatanodeRegistration(, storageID=DS-532990984-, infoPort=50075, ipcPort=50020):DataXceiver
org.apache.hadoop.util.DiskChecker$DiskOutOfSpaceException: No space left on device
        at org.apache.hadoop.hdfs.server.datanode.DataNode.checkDiskError(
        at org.apache.hadoop.hdfs.server.datanode.BlockReceiver.receivePacket(
        at org.apache.hadoop.hdfs.server.datanode.BlockReceiver.receiveBlock(
        at org.apache.hadoop.hdfs.server.datanode.DataXceiver.writeBlock(


Not sure whether this is the root cause of the namenode shutting down issue?


New error raised when I was trying to restart the namenode?


2014-09-28 11:25:06,202 ERROR org.apache.hadoop.hdfs.server.namenode.FSNamesystem: FSNamesystem initialization failed. Incorrect data format. logVersion is -31 but writables.length is 0.
        at org.apache.hadoop.hdfs.server.namenode.FSEditLog.loadFSEdits(
        at org.apache.hadoop.hdfs.server.namenode.FSImage.loadFSEdits(
        at org.apache.hadoop.hdfs.server.namenode.FSImage.loadFSImage(
        at org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(
        at org.apache.hadoop.hdfs.server.namenode.FSDirectory.loadFSImage(
        at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.initialize(
        at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.<init>(
        at org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(
        at org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(
        at org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(
        at org.apache.hadoop.hdfs.server.namenode.NameNode.main(


Is there anyone knows about it ?  is it possible to fix the imagne and editor files?




Kevin Jin


Re: namdenode failed

Expert Contributor
Looks like your edits file is corrupted, can you try replacing your current from previous checkpoints and see if that resolves the issue...

Have you upgraded to a new version of hadoop recently ?
Em Jay

Re: namdenode failed

Expert Contributor
Also check whether your namenode metadata directory does have enough space to write new metadata..
Em Jay