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 "Harsh J (Resolved) (JIRA)" <ji...@apache.org> on 2011/12/31 10:28:31 UTC
[jira] [Resolved] (MAPREDUCE-46) mapred/local/jobTracker is not
cleanup correctly
[ https://issues.apache.org/jira/browse/MAPREDUCE-46?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Harsh J resolved MAPREDUCE-46.
------------------------------
Resolution: Cannot Reproduce
Haven't noticed this issue in branch-1.
> mapred/local/jobTracker is not cleanup correctly
> ------------------------------------------------
>
> Key: MAPREDUCE-46
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-46
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Reporter: Benjamin Francisoud
> Attachments: patch-JobTracker-cleanup-submission-dir-0.14.0.diff
>
>
> Jobtracker store 1.jar file and 1 .xml per job in /srv/hadoop/var/mapred/local/jobTracker.
> They seems to be correctly delete in most cases BUT not when a job is launch with
> Map total: 0 and Reduce total: 0
> This happen when the job doesn't find any input file to process.
> After few months, lots of disk space is lost because of that.
> This issue is different from HADOOP-2427 since it's on the jobtracker, not on the nodes, but it may be related in some way in the code (my 2 cents).
--
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