[
https://issues.apache.org/jira/browse/MAPREDUCE-1682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer resolved MAPREDUCE-1682.
-----------------------------------------
Resolution: Fixed
Likely fixed.
> 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
> Assignee: Arun C Murthy
> Attachments: mapreduce-1682-ydh.txt
>
>
> 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 was sent by Atlassian JIRA
(v6.2#6252)
