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 "Hemanth Yamijala (JIRA)" <ji...@apache.org> on 2009/02/18 09:55:01 UTC

[jira] Updated: (HADOOP-5248) Job directories could remain undeleted in some scenarios after job completes.

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

Hemanth Yamijala updated HADOOP-5248:
-------------------------------------

         Priority: Blocker  (was: Major)
    Fix Version/s: 0.20.0

After discussion with Sameer and Devaraj, marking this a blocker for Hadoop 0.20.

> Job directories could remain undeleted in some scenarios after job completes.
> -----------------------------------------------------------------------------
>
>                 Key: HADOOP-5248
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5248
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>            Reporter: Hemanth Yamijala
>            Priority: Blocker
>             Fix For: 0.20.0
>
>
> I observed a couple of times that when a job has completed, its job directories were not cleaned up. In discussion, it seems like there is a condition when only reduces from a job are run on a machine and no maps, the TT does not get a signal from the JT to delete the files and could be left behind. FYI, JVM reuse was enabled at the time. I can confirm that 'KillJobAction' was not received by the TT.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.