[HDFS-5367] Restoring namenode storage locks namenode due to unnecessary fsimage write

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.2.1
• Fix Version/s: 1.3.0
• Hadoop Flags: Reviewed
• Assignee: yunjiong zhao
• Reporter: yunjiong zhao
• Created: 16/Oct/13 08:06
• Updated: 21/Oct/13 08:21
• Resolved: 17/Oct/13 20:27

Description

Our cluster have 40G fsimage, we write one copy of edit log to NFS.
After NFS temporary failed, when doing checkpoint, NameNode try to recover it, and it will save 40G fsimage to NFS, it takes some time (> 40G/128MB/s = 320 seconds) , and it locked FSNamesystem, and this bring down our cluster.

Issue Links

• relates to: HDFS-5396 FSImage.getFsImageName should check whether fsimage exists