[HDFS-30] Simulated DataNode crashes NameNode

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Assignee: Unassigned
• Reporter: Hairong Kuang
• Created: 04/Mar/09 19:22
• Updated: 20/Jun/09 07:41

Description

INFO org.apache.hadoop.hdfs.StateChange: BLOCK* NameSystem.processReport: block blk_448_1 on
XX size 10 does not belong to any file.
INFO org.apache.hadoop.hdfs.StateChange: BLOCK* NameSystem.addToInvalidates: blk_448 is added
to invalidSet of XX
INFO org.apache.hadoop.hdfs.StateChange: BLOCK* NameSystem.processReport: block blk_447_1 on
XX size 10 does not belong to any file.
INFO org.apache.hadoop.hdfs.StateChange: BLOCK* NameSystem.addToInvalidates: blk_447 is added
to invalidSet of XX
WARN org.apache.hadoop.hdfs.server.namenode.FSNamesystem: ReplicationMonitor thread received
Runtime exception. java.lang.IllegalStateException: generationStamp (=1) == GenerationStamp.WILDCARD_STAMP
INFO org.apache.hadoop.hdfs.server.namenode.NameNode: SHUTDOWN_MSG:
/************************************************************
SHUTDOWN_MSG: Shutting down NameNode at YY
************************************************************/

Issue Links

• is related to: HADOOP-5384 DataNodeCluster should not create blocks with generationStamp == 1