[
https://issues.apache.org/jira/browse/MAPREDUCE-5351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
jandyfish updated MAPREDUCE-5351:
---------------------------------
Attachment: JobInProgress_JobHistory.patch
find a bug :
open a filesystem when JobHistory create userLogFile,but this filesystem
instance will not be close,and it still cache in FileSystem.cache。
i comminited this svn patch JobInProcess_JobHistory.path。i hope it can help.
> JobTracker memory leak caused by CleanupQueue reopening FileSystem
> ------------------------------------------------------------------
>
> Key: MAPREDUCE-5351
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5351
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: jobtracker
> Affects Versions: 1.1.2
> Reporter: Sandy Ryza
> Assignee: Sandy Ryza
> Priority: Critical
> Fix For: 1-win, 1.2.1
>
> Attachments: JobInProgress_JobHistory.patch, MAPREDUCE-5351-1.patch,
> MAPREDUCE-5351-2.patch, MAPREDUCE-5351-addendum-1.patch,
> MAPREDUCE-5351-addendum.patch, MAPREDUCE-5351.patch
>
>
> When a job is completed, closeAllForUGI is called to close all the cached
> FileSystems in the FileSystem cache. However, the CleanupQueue may run after
> this occurs and call FileSystem.get() to delete the staging directory, adding
> a FileSystem to the cache that will never be closed.
> People on the user-list have reported this causing their JobTrackers to OOME
> every two weeks.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
