Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hadoop-dev@lucene.apache.org
Message-ID: <25142090.1149034770669.JavaMail.jira@brutus>
Date: Wed, 31 May 2006 00:19:30 +0000 (GMT+00:00)
From: "Sameer Paranjpye (JIRA)" <jira@apache.org>
To: hadoop-dev@lucene.apache.org
Subject: [jira] Updated: (HADOOP-225) tasks are left over when a job fails
In-Reply-To: <14555788.1147888325909.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

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

Sameer Paranjpye updated HADOOP-225:
------------------------------------

    Fix Version: 0.4
        Version: 0.2

> 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
>     Reporter: Yoram Arnon
>     Priority: Minor
>      Fix For: 0.4

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