[
https://issues.apache.org/jira/browse/MAPREDUCE-5351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13848154#comment-13848154
]
viswanathan commented on MAPREDUCE-5351:
----------------------------------------
Hi Chris,
For that JT hangs, you have asked to disable the hadoop user history
location. So doing this will solve the problem. What exactly happens if I
set this value to NONE. By setting this value, JT heap memory will not
increase as much like now.
Also I'm using the version 1.2.1, when the JT memory reaches 6.68/8.89 GB
it start hangs every ten days. Not able to submit the job and UI is not
loading at all.
Please 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.4#6159)
