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 "Doug Cutting (JIRA)" <ji...@apache.org> on 2006/06/28 23:11:55 UTC

[jira] Updated: (HADOOP-225) tasks are left over when a job fails

     [ http://issues.apache.org/jira/browse/HADOOP-225?page=all ]

Doug Cutting updated HADOOP-225:
--------------------------------

    Fix Version: 0.5.0
                     (was: 0.4.0)

> tasks are left over when a job fails
> ------------------------------------
>
>          Key: HADOOP-225
>          URL: http://issues.apache.org/jira/browse/HADOOP-225
>      Project: Hadoop
>         Type: Bug

>   Components: mapred
>     Versions: 0.2.0
>     Reporter: Yoram Arnon
>     Priority: Minor
>      Fix For: 0.5.0

>
> when jobs are stopped or otherwise fail, tasks are often left around.
> the job tracker shows that there are map or reduce (mostly reduce) tasks running, when no job is running.
> these accumulate over time.
> eventually there are so many of those, that the job tracker can't launch new tasks, requiring a restart of the MR cluster.

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