[HDFS-5247] Namenode should close editlog and unlock storage when removing failed storage dir

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.2.1
• Fix Version/s: 1.2.1
• Component/s: namenode
• Assignee: yunjiong zhao
• Reporter: yunjiong zhao
• Created: 23/Sep/13 02:57
• Updated: 16/Oct/13 17:45

Description

When one of dfs.name.dir failed, namenode didn't close editlog and unlock the storage:
java 24764 hadoop 78uW REG 252,32 0 393219 /volume1/nn/dfs/in_use.lock (deleted)
java 24764 hadoop 107u REG 252,32 1155072 393229 /volume1/nn/dfs/current/edits.new (deleted)
java 24764 hadoop 119u REG 252,32 0 393238 /volume1/nn/dfs/current/fstime.tmp
java 24764 hadoop 140u REG 252,32 1761805 393239 /volume1/nn/dfs/current/edits

If this dir is limit of space, then restore this storage may fail.