[HADOOP-3709] Lock hierarchy violation in namenode while handling hearbeats

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Invalid
• Assignee: Unassigned
• Reporter: Dhruba Borthakur
• Created: 07/Jul/08 22:38
• Updated: 08/Jul/09 16:43
• Resolved: 01/Aug/08 07:48

Description

The heartbeat processing code recently got rearranged via HADOOP-3254. FSNamesystem.handleHeartbeat acquires the hearbeat lock and then invoke blockReportProcessed. This method tries to acquire the global FSNamesystem lock. This is a lock hierarchy violation. This leads to deadlock.

The heatbeat processing code should acquire only the heartbeat lock. It should not acquire the global lock, otherwise heartprocessing become too heavyweight.

This code occurs only on trunk and not o 018 branch. Surprise!

Issue Links

• is part of: HADOOP-3620 Namenode should synchronously resolve a datanode's network location when the datanode registers
• is related to: HADOOP-3002 HDFS should not remove blocks while in safemode.