Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Message-ID: <60491975.1257759287750.JavaMail.jira@brutus>
Date: Mon, 9 Nov 2009 09:34:47 +0000 (UTC)
From: "Vinod K V (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Subject: [jira] Resolved: (MAPREDUCE-515)
 CapacityTaskScheduler.MapSchedulingMgr.killTasksFromJob() will not work as
 expected
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Vinod K V resolved MAPREDUCE-515.
---------------------------------

    Resolution: Invalid

Preemption is removed after HADOOP-5726. This issue is no longer valid.

> CapacityTaskScheduler.MapSchedulingMgr.killTasksFromJob() will not work as expected
> -----------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-515
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-515
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>            Reporter: Amar Kamat
>
> Once capacity-scheduler decides on killing tasks, it selects running-jobs from the queue and issues {{killTasksFromJob()}}. The order in which it kills is as follows
> - non-local maps
> - local maps
> _Killing non-local maps :_
> The code here uses {{JobInProgress.getNonLocalRunningMaps()}}. HADOOP-2119 introduced this for handling cases like _random-writer_. Hence this api will return an empty structure if there are reducers in the job. Hence the code fails to serve its purpose. 

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