hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arun C Murthy (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-639) task cleanup messages can get lost, causing task trackers to keep tasks forever
Date Wed, 06 Dec 2006 05:17:22 GMT
    [ http://issues.apache.org/jira/browse/HADOOP-639?page=comments#action_12455867 ] 
            
Arun C Murthy commented on HADOOP-639:
--------------------------------------

Mahadev, there is a corner-case which will fail if we take the RunningJobs.cleanup route:
if after the job 'cleanup' the JT allocates a new task to the same TT, that task will fail
since the job-dir is gone, which is why this patch will rely on the KillJobAction (sent by
JT after the job completes/killed/fails) to cleanup the job-dir... your take?

> task cleanup messages can get lost, causing task trackers to keep tasks forever
> -------------------------------------------------------------------------------
>
>                 Key: HADOOP-639
>                 URL: http://issues.apache.org/jira/browse/HADOOP-639
>             Project: Hadoop
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.7.2
>            Reporter: Owen O'Malley
>         Assigned To: Arun C Murthy
>         Attachments: HADOOP-639_1.patch, HADOOP-639_2_20061130.patch, HADOOP-639_3_20061201.patch,
HADOOP-639_4_20061205.patch
>
>
> If the pollForTaskWithClosedJob call from a job tracker to a task tracker times out when
a job completes, the tasks are never cleaned up. This can cause the mini m/r cluster to hang
on shutdown, but also is a resource leak.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message