Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <481141197.1234973821801.JavaMail.jira@brutus>
Date: Wed, 18 Feb 2009 08:17:01 -0800 (PST)
From: "Devaraj Das (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Assigned: (HADOOP-5248) Job directories could remain
 undeleted in some scenarios after job completes.
In-Reply-To: <1946806587.1234514039793.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Devaraj Das reassigned HADOOP-5248:
-----------------------------------

    Assignee: 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
>
>
> 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.