[HDFS-3277] fail over to loading a different FSImage if the first one we try to load is corrupt

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0.0-alpha1
• Fix Version/s: 2.1.0-beta
• Hadoop Flags: Reviewed
• Assignee: Andrew Wang
• Reporter: Colin McCabe
• Created: 13/Apr/12 23:29
• Updated: 12/May/16 18:13
• Resolved: 14/Mar/13 18:20

Description

Most users store multiple copies of the FSImage in order to prevent catastrophic data loss if a hard disk fails. However, our image loading code is currently not set up to start reading another FSImage if loading the first one does not succeed. We should add this capability.

We should also be sure to remove the FSImage directory that failed from the list of FSImage directories to write to, in the way we normally do when a write (as opopsed to read) fails.

Issue Links

• is related to: HDFS-3736 Failure in starting NN due to fsimage loading failure
• relates to: HDFS-3049 During the normal loading NN startup process, fall back on a different EditLog if we see one that is corrupt