[HADOOP-3337] Name-node fails to start because DatanodeInfo format changed.

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 0.18.0
• Fix Version/s: 0.18.0
• Assignee: Tsz-wo Sze
• Reporter: Konstantin Shvachko
• Created: 02/May/08 00:36
• Updated: 08/Jul/09 16:43
• Resolved: 04/May/08 19:29

Description

HADOOP-3283 introduced a new field ipcPort in DatanodeInfo, which was not reflected in the reading/writing file system image files.
Particularly, reading edits generated by the previous version of hadoop throws the following exception:

08/05/02 00:02:50 ERROR dfs.NameNode: java.lang.IllegalArgumentException: No enum const class org.apache.hadoop.dfs.DatanodeInfo$AdminStates.0?
/56.313
	at java.lang.Enum.valueOf(Enum.java:192)
	at org.apache.hadoop.io.WritableUtils.readEnum(WritableUtils.java:399)
	at org.apache.hadoop.dfs.DatanodeInfo.readFields(DatanodeInfo.java:318)
	at org.apache.hadoop.io.ArrayWritable.readFields(ArrayWritable.java:90)
	at org.apache.hadoop.dfs.FSEditLog.loadFSEdits(FSEditLog.java:499)
	at org.apache.hadoop.dfs.FSImage.loadFSEdits(FSImage.java:794)
	at org.apache.hadoop.dfs.FSImage.loadFSImage(FSImage.java:664)
	at org.apache.hadoop.dfs.FSImage.recoverTransitionRead(FSImage.java:280)
	at org.apache.hadoop.dfs.FSDirectory.loadFSImage(FSDirectory.java:81)
	at org.apache.hadoop.dfs.FSNamesystem.initialize(FSNamesystem.java:276)
	at org.apache.hadoop.dfs.FSNamesystem.<init>(FSNamesystem.java:257)
	at org.apache.hadoop.dfs.NameNode.initialize(NameNode.java:133)
	at org.apache.hadoop.dfs.NameNode.<init>(NameNode.java:178)
	at org.apache.hadoop.dfs.NameNode.<init>(NameNode.java:164)
	at org.apache.hadoop.dfs.NameNode.createNameNode(NameNode.java:777)
	at org.apache.hadoop.dfs.NameNode.main(NameNode.java:786)

and startup fails.

Issue Links

• relates to: HADOOP-3329 DatanodeDescriptor objects stored in FSImage may be out dated.