You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-user@hadoop.apache.org by Otis Gospodnetic <ot...@yahoo.com> on 2008/07/04 02:00:58 UTC

ERROR dfs.NameNode - java.io.EOFException

Hi,

Using Hadoop 0.16.2, I am seeing seeing the following in the NN log:

2008-07-03 19:46:26,715 ERROR dfs.NameNode - java.io.EOFException
        at java.io.DataInputStream.readFully(DataInputStream.java:180)
        at org.apache.hadoop.io.UTF8.readFields(UTF8.java:106)
        at org.apache.hadoop.io.ArrayWritable.readFields(ArrayWritable.java:90)
        at org.apache.hadoop.dfs.FSEditLog.loadFSEdits(FSEditLog.java:433)
        at org.apache.hadoop.dfs.FSImage.loadFSEdits(FSImage.java:756)
        at org.apache.hadoop.dfs.FSImage.loadFSImage(FSImage.java:639)
        at org.apache.hadoop.dfs.FSImage.recoverTransitionRead(FSImage.java:222)
        at org.apache.hadoop.dfs.FSDirectory.loadFSImage(FSDirectory.java:79)
        at org.apache.hadoop.dfs.FSNamesystem.initialize(FSNamesystem.java:254)
        at org.apache.hadoop.dfs.FSNamesystem.<init>(FSNamesystem.java:235)
        at org.apache.hadoop.dfs.NameNode.initialize(NameNode.java:131)
        at org.apache.hadoop.dfs.NameNode.<init>(NameNode.java:176)
        at org.apache.hadoop.dfs.NameNode.<init>(NameNode.java:162)
        at org.apache.hadoop.dfs.NameNode.createNameNode(NameNode.java:846)
        at org.apache.hadoop.dfs.NameNode.main(NameNode.java:855)

The exception doesn't include the name and location of the file whose reading is failing and causing EOFException :(
But it looks like it's the fsedit log (the "edits" file, I think).

There is no secondary NN in the cluster.

Is there any way I can revive this NN?  Any way to "fix" the corrupt "edits" file?

Thanks,
Otis