hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amareshwari Sriramadasu (JIRA)" <j...@apache.org>
Subject [jira] Created: (HADOOP-5408) Task left in RUNNING state even after the job completion
Date Thu, 05 Mar 2009 10:25:58 GMT
Task left in RUNNING state even after the job completion
--------------------------------------------------------

                 Key: HADOOP-5408
                 URL: https://issues.apache.org/jira/browse/HADOOP-5408
             Project: Hadoop Core
          Issue Type: Bug
          Components: mapred
            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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message