You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2014/07/21 23:30:42 UTC
[jira] [Resolved] (MAPREDUCE-431) Task left in RUNNING state even
after the job completion
[ https://issues.apache.org/jira/browse/MAPREDUCE-431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Allen Wittenauer resolved MAPREDUCE-431.
----------------------------------------
Resolution: Fixed
Likely stale.
> Task left in RUNNING state even after the job completion
> --------------------------------------------------------
>
> Key: MAPREDUCE-431
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-431
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: jobtracker
> Reporter: Amareshwari Sriramadasu
> Priority: Minor
>
> Task could be left in RUNNING state in the following scenario:
> 1. Job was killed from command-line.
> 2. TaskTracker running the task didnt come back.
> 3. JobTracker marks the tracker as lost, but since Job is not RUNNING, it does not change the Task's state.
> The code doing the same in JobTracker.lostTaskTracker method is :
> {noformat}
> // if the job is done, we don't want to change anything
> if (job.getStatus().getRunState() == JobStatus.RUNNING ||
> job.getStatus().getRunState() == JobStatus.PREP) {
> job.failedTask(tip, taskId, ("Lost task tracker: " + trackerName),
> ........
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.2#6252)