[HADOOP-4810] Data lost at cluster startup time

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 0.18.2
• Fix Version/s: 0.18.3
• Hadoop Flags: Reviewed
• Assignee: Hairong Kuang
• Reporter: Hairong Kuang
• Created: 09/Dec/08 20:01
• Updated: 08/Jul/09 16:43
• Resolved: 16/Dec/08 23:32

Description

hadoop dfs -cat file1 returns
dfs.DFSClient: Could not obtain block blk_XX_0 from any node: java.io.IOException: No live nodes contain current block

Tracing the history of the block from NN log, we found
WARN org.apache.hadoop.fs.FSNamesystem: Inconsistent size for block blk_-6160940519231606858_0 reported from A1.A2.A3.A4:50010 current size is 9303872 reported size is 262144
WARN org.apache.hadoop.fs.FSNamesystem: Deleting block blk_-6160940519231606858_0 from A1.A2.A3.A4:50010
INFO org.apache.hadoop.dfs.StateChange: DIR* NameSystem.invalidateBlock: blk_-6160940519231606858_0 on A1.A2.A3.A4:50010
WARN org.apache.hadoop.fs.FSNamesystem: Error in deleting bad block blk_-6160940519231606858_0 org.apache.hadoop.dfs.SafeModeException: Cannot invalidate block blk_-6160940519231606858_0. Name node is in safe mode.
WARN org.apache.hadoop.fs.FSNamesystem: Inconsistent size for block blk_-6160940519231606858_0 reported from B1.B2.B3.B4:50010 current size is 9303872 reported size is 306688
WARN org.apache.hadoop.fs.FSNamesystem: Deleting block blk_-6160940519231606858_0 from B1.B2.B3.B4:50010
INFO org.apache.hadoop.dfs.StateChange: DIR* NameSystem.invalidateBlock: blk_-6160940519231606858_0 on B1.B2.B3.B4:50010
WARN org.apache.hadoop.fs.FSNamesystem: Error in deleting bad block blk_-6160940519231606858_0 org.apache.hadoop.dfs.SafeModeException: Cannot invalidate block blk_-6160940519231606858_0. Name node is in safe mode.
INFO org.apache.hadoop.dfs.StateChange: BLOCK* NameSystem.chooseExcessReplicates: (C1.C2.C3.C4:50010, blk_-6160940519231606858_0) is added to recentInvalidateSets
INFO org.apache.hadoop.dfs.StateChange: BLOCK* NameSystem.chooseExcessReplicates: (D1.D2.D3.D4:50010, blk_-6160940519231606858_0) is added to recentInvalidateSets
INFO org.apache.hadoop.dfs.StateChange: BLOCK* ask C1.C2.C3.C4:50010 to delete blk_-6160940519231606858_0
INFO org.apache.hadoop.dfs.StateChange: BLOCK* ask D1.D2.D3.D4:50010 to delete blk_-6160940519231606858_0

Issue Links

• is related to: HDFS-142 In 0.20, move blocks being written into a blocksBeingWritten directory
• relates to: HDFS-48 NN should check a block's length even if the block is not a new block when processing a blockreport