[
https://issues.apache.org/jira/browse/HADOOP-2427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arun C Murthy updated HADOOP-2427:
----------------------------------
Status: Open (was: Patch Available)
I don't think this is the right approach, we really shouldn't be adding more
'cleanup' methods when we already have one in TaskTracker.TaskInProgress,
please do the necessary cleanup there if possible.
Please don't add more to MRConstants.java, WORKDIR should belong to
TaskTracker.TaskInProgress.
> Cleanup of mapred.local.dir after maptask is complete
> -----------------------------------------------------
>
> Key: HADOOP-2427
> URL: https://issues.apache.org/jira/browse/HADOOP-2427
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.15.1
> Reporter: lohit vijayarenu
> Assignee: Amareshwari Sriramadasu
> Fix For: 0.18.0
>
> Attachments: patch-2427.txt
>
>
> I see that after a map task is complete, its working directory
> (mapred.local.dir)/taskTracker/jobcache/<jobid>/<task_dir> is not deleted
> untill the job is complete. If map out files are stored in there, could this
> be created in different directory and the working directory cleaned up after
> map task is complete. One problem we are seeing is, if a map task creates
> files temporary files, they get accumulated and we may run out of disk space
> thus failing the job. Relying on the user to cleanup all temp files created
> is be error prone.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
