[HADOOP-3382] Memory leak when files are not cleanly closed

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 0.15.0
• Fix Version/s: 0.17.0
• Hadoop Flags: Reviewed
• Release Note: Fixed a memory leak associated with 'abandoned' files (i.e. not cleanly closed). This held up significant amounts of memory depending on activity and how long NameNode has been running.
• Assignee: Raghu Angadi
• Reporter: Raghu Angadi
• Created: 13/May/08 18:40
• Updated: 08/Jul/09 16:43
• Resolved: 15/May/08 18:33

Description

FSNamesystem.internalReleaseCreate() in invoked on files that are open for writing but not cleanly closed. e.g. when client invokes abandonFileInProgress() or when lease expires. It deletes the last block if it has a length of zero. The block is deleted from the file INode but not from blocksMap. Then leaves a reference to such file until NameNode is restarted. When this happens HADOOP-3381 multiplies amount of memory leak.