[
https://issues.apache.org/jira/browse/MAPREDUCE-2762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13128945#comment-13128945
]
Vinod Kumar Vavilapalli commented on MAPREDUCE-2762:
----------------------------------------------------
Why can't we simply move the {{cleanupStagingDir()}} operation into MRAppMaster
itself from the Job. In that case, we don't need this complex event handling
from Job into MRAppMaster and then back into Job. Essentially
{code}
class MRAppMasster {
.....
@Override
public void stop() {
super.stop(); // Stop all services
cleanupStagingDir(); // Cleanup the dir now.
}
.....
}
{code}
I get a feeling that there is a disconnect here and I may be missing something,
am I?
> [MR-279] - Cleanup staging dir after job completion
> ---------------------------------------------------
>
> Key: MAPREDUCE-2762
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2762
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: 0.23.0
> Reporter: Ramya Sunil
> Assignee: Mahadev konar
> Priority: Blocker
> Fix For: 0.23.0
>
> Attachments: MAPREDUCE-2762.patch, MAPREDUCE-2762.patch,
> MAPREDUCE-2762.patch, MAPREDUCE-2762.patch
>
>
> The files created under the staging dir have to be deleted after job
> completion. Currently, all job.* files remain forever in the
> ${yarn.apps.stagingDir}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
