[HDFS-7253] getBlockLocationsUpdateTimes missing handle exception may cause fsLock dead lock

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Invalid
• Affects Version/s: 2.2.0
• Component/s: namenode
• Assignee: Unassigned Assign to me
• Reporter: Carrey Zhan
• Created: 15/Oct/14 09:52
• Updated: 15/Oct/14 12:14
• Resolved: 15/Oct/14 12:07

Description

One day my active namenode hanged and I dumped the program stacks by jstack.In the stacks file, I saw most threads were waiting FSNamesystem.fsLock, both readLock and writeLock were unacquirable, but no thread was holding writeLock.
I tried to access the web interface of this namenode but was blocked. and I tried to failover the active node to another namenode manually (zkfs did not discover this node was hanging) but it was also failed. So I killed this namenode trying to recover the production environment, then the failover was triggered, standby nn transited to active, and then, the new active namenode hanged.
My following steps are useless and can be ignored. At last, I thought it was caused by an incorrect lock handling in FSNamesystem.getBlockLocationsUpdateTimes, which I will describe in the first comment.

Issue Links

• relates to: HDFS-7045 Fix NameNode deadlock when opening file under /.reserved path