[
https://issues.apache.org/jira/browse/HDFS-87?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12835945#action_12835945
]
dhruba borthakur commented on HDFS-87:
--------------------------------------
The issue of having an truncated last-entry in the edit slog is an old issue
and this problem should not be there in the current trunk (after we introduced
the preallocation of blocks in the edits log and OP_INVALID end marker).
I am closing this for now
> NameNode startup fails if edit log terminates prematurely
> ---------------------------------------------------------
>
> Key: HDFS-87
> URL: https://issues.apache.org/jira/browse/HDFS-87
> Project: Hadoop HDFS
> Issue Type: Bug
> Environment: ~50 node cluster
> Reporter: Bryan Pendleton
> Attachments: fixNameNodeStartup.patch
>
>
> I ran out of space on the device that stores the edit log, resulting in an
> edit log that is truncated mid transaction.
> Ideally, the NameNode should start up, in SafeMode or the like, whenever this
> happens. Right now, you get this stack trace:
> 2006-12-12 15:33:57,212 ERROR org.apache.hadoop.dfs.NameNode:
> java.io.EOFExcepti
> on
> at java.io.DataInputStream.readUnsignedShort(DataInputStream.java:310)
> at org.apache.hadoop.io.UTF8.readFields(UTF8.java:104)
> at org.apache.hadoop.dfs.FSEditLog.loadFSEdits(FSEditLog.java:227)
> at org.apache.hadoop.dfs.FSImage.loadFSImage(FSImage.java:191)
> at org.apache.hadoop.dfs.FSDirectory.loadFSImage(FSDirectory.java:320)
> at org.apache.hadoop.dfs.FSNamesystem.<init>(FSNamesystem.java:226)
> at org.apache.hadoop.dfs.NameNode.<init>(NameNode.java:146)
> at org.apache.hadoop.dfs.NameNode.<init>(NameNode.java:138)
> at org.apache.hadoop.dfs.NameNode.main(NameNode.java:589)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
