hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-5248) Job directories could remain undeleted in some scenarios after job completes.
Date Thu, 26 Feb 2009 15:13:06 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-5248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677027#action_12677027
] 

Hudson commented on HADOOP-5248:
--------------------------------

Integrated in Hadoop-trunk #766 (See [http://hudson.zones.apache.org/hudson/job/Hadoop-trunk/766/])
    . A testcase that checks for the existence of job directory after the job completes. Fails
if it exists. Contributed by Devaraj Das.


> 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
>            Assignee: Devaraj Das
>            Priority: Blocker
>             Fix For: 0.20.0
>
>         Attachments: 5248-testcase.patch, 5248.patch
>
>
> 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.


Mime
View raw message