You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Amareshwari Sriramadasu (JIRA)" <ji...@apache.org> on 2008/07/14 06:31:31 UTC

[jira] Updated: (HADOOP-2427) Cleanup of mapred.local.dir after maptask is complete

     [ https://issues.apache.org/jira/browse/HADOOP-2427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Amareshwari Sriramadasu updated HADOOP-2427:
--------------------------------------------

    Release Note: The current working directory of a task, i.e. ${mapred.local.dir}/taskTracker/jobcache/<jobid>/<task_dir>/work is cleanedup, as soon as the task is finished.

> 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, 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.