[
https://issues.apache.org/jira/browse/HDFS-87?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dhruba borthakur resolved HDFS-87.
----------------------------------
Resolution: Not A Problem
> 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.
