You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2014/07/21 23:08:39 UTC
[jira] [Resolved] (MAPREDUCE-146) Stale job files in mapred system
directory
[ https://issues.apache.org/jira/browse/MAPREDUCE-146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Allen Wittenauer resolved MAPREDUCE-146.
----------------------------------------
Resolution: Not a Problem
With split calculations moved and job submission changed, this is no longer a problem. Closing.
> Stale job files in mapred system directory
> ------------------------------------------
>
> Key: MAPREDUCE-146
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-146
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Reporter: Vinod Kumar Vavilapalli
>
> In one scenario, job client uploaded the job split file and job jar onto the mapred system directory but got killed before the actual job got submitted and/or before the job got known to the JT. In such situations, the split and jar files are left as garbage as JT doesn't know of the job yet. On a long running JT, this garbage can accumulate.
--
This message was sent by Atlassian JIRA
(v6.2#6252)