[
https://issues.apache.org/jira/browse/MAPREDUCE-5508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13767828#comment-13767828
]
Chris Nauroth commented on MAPREDUCE-5508:
------------------------------------------
bq. ...race condition between DistributedFileSystem#close() and
FileSystem#close()...
I've been meaning to file an issue for this one, so I just created HDFS-5211.
Xi, do you mind if we handle that issue separately and keep this issue focused
on fixing the JobTracker memory leak? It's an HDFS bug that impacts any
multi-threaded usage of {{DistributedFileSystem}} (not just this MapReduce code
path), and I think we can fix the root cause there in HDFS.
IOW, we don't need to let the presence of that bug influence the way we code a
fix for this one, because I think we can fix both. :-)
> 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
> Attachments: 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
