Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Message-ID: <255846735.35971270615353530.JavaMail.jira@brutus.apache.org>
Date: Wed, 7 Apr 2010 04:42:33 +0000 (UTC)
From: "Amareshwari Sriramadasu (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Subject: [jira] Commented: (MAPREDUCE-1682) Tasks should not be scheduled
 after tip is killed/failed.
In-Reply-To: <996392346.35901270615113575.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/MAPREDUCE-1682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12854339#action_12854339 ] 

Amareshwari Sriramadasu commented on MAPREDUCE-1682:
----------------------------------------------------

A quick look at the JobInProgress code says "In JobInProgress.findSpeculativeTask(), tip.isRunnable() check is not done,
whereas the method JobInProgress.findTaskFromList() does the check to skip failed/killed tips".

The bug is not there in 0.21 or trunk (got fixed in HADOOP:2141), it is there only in branch 0.20.

> Tasks should not be scheduled after tip is killed/failed.
> ---------------------------------------------------------
>
>                 Key: MAPREDUCE-1682
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1682
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: jobtracker
>            Reporter: Amareshwari Sriramadasu
>             Fix For: 0.20.3
>
>
> We have seen the following scenario in our cluster:
> A job got marked failed, because four attempts of a TIP failed. This would kill all the map and reduce tips. Then a job-cleanup attempt is launched.
> The job-cleanup attempt failed because it could not report status for 10 minutes. There are 3 such job-cleanup attempts leading the job to get killed after 1/2 hour.
> While waiting for the job cleanup to finish, JobTracker scheduled many tasks of the job on TaskTrackers and sent a KillTaskAction in the next heartbeat. 
> This is just wasting lots of resources, we should avoid scheduling tasks of a tip once the tip is killed/failed.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.