[
https://issues.apache.org/jira/browse/MAPREDUCE-5508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13800132#comment-13800132
]
viswanathan commented on MAPREDUCE-5508:
----------------------------------------
Hi Chris,
Hope this 3 patches only need to apply, if any other patches missing please let
me know.
https://issues.apache.org/jira/secure/attachment/12590105/MAPREDUCE-5351-2.patch
https://issues.apache.org/jira/secure/attachment/12590672/MAPREDUCE-5351-addendum-1.patch
https://issues.apache.org/jira/secure/attachment/12604722/MAPREDUCE-5508.3.patch
Also have downloaded the latest hadoop-1.2.1 version, while building jar I'm
getting snapshot version(i.e., hadoop-core-1.2.2-SNAPSHOT.jar) jars. Is these
because of some other changes are made in that version.
Hope this will not be a problem for updating in production environment.
Thanks,
> JobTracker memory leak caused by unreleased FileSystem objects in
> JobInProgress#cleanupJob
> ------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-5508
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5508
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: jobtracker
> Affects Versions: 1-win, 1.2.1
> Reporter: Xi Fang
> Assignee: Xi Fang
> Priority: Critical
> Fix For: 1-win, 1.3.0
>
> Attachments: MAPREDUCE-5508.1.patch, MAPREDUCE-5508.2.patch,
> MAPREDUCE-5508.3.patch, MAPREDUCE-5508.patch
>
>
> MAPREDUCE-5351 fixed a memory leak problem but introducing another filesystem
> object (see "tempDirFs") that is not properly released.
> {code} JobInProgress#cleanupJob()
> void cleanupJob() {
> ...
> tempDirFs = jobTempDirPath.getFileSystem(conf);
> CleanupQueue.getInstance().addToQueue(
> new PathDeletionContext(jobTempDirPath, conf, userUGI, jobId));
> ...
> if (tempDirFs != fs) {
> try {
> fs.close();
> } catch (IOException ie) {
> ...
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.1#6144)