[HDFS-3045] fsck move should bail on a file if it can't create a block file

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Component/s: namenode
• Assignee: Colin McCabe
• Reporter: Eli Collins
• Created: 05/Mar/12 16:48
• Updated: 22/Mar/12 22:44
• Resolved: 22/Mar/12 22:44

Description

NamenodeFsck#lostFoundMove, when it fails to create a file for a block continues on to the next block (There's a comment "perhaps we should bail out here..." but it doesn't). It should instead fail the move for that particular file (unwind the directory creation and not delete the original file). Otherwise a transient failure speaking to the NN means this block is lost forever.

Issue Links

• relates to: HDFS-3044 fsck move should be non-destructive by default