[HDFS-2865] Standby namenode gets a "cannot lock storage" exception during startup

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Invalid
• Affects Version/s: HA branch (HDFS-1623)
• Component/s: ha, namenode
• Assignee: Hari Mankude
• Reporter: Hari Mankude
• Created: 31/Jan/12 19:49
• Updated: 09/Feb/12 19:42
• Resolved: 09/Feb/12 19:42

Description

Standby NN is restarted. This is a follow-on to hdfs-2863. In this setup, dfs.edits.dir is different from dfs.shared.edits.dir. During startup, standby NN fails to acquire lock on the dfs.edits.dir. If standby NN is restarted again, it seems to work fine.

Issue Links

• relates to: HDFS-2877 If locking of a storage dir fails, it will remove the other NN's lock file on exit