You are viewing a plain text version of this content. The canonical link for it is here.

Posted to mapreduce-dev@hadoop.apache.org by "Amar Kamat (JIRA)" <ji...@apache.org> on 2009/07/14 08:49:14 UTC

[jira] Created: (MAPREDUCE-758) JobInProgressListener events might be garbled

JobInProgressListener events might be garbled
---------------------------------------------

                 Key: MAPREDUCE-758
                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-758
             Project: Hadoop Map/Reduce
          Issue Type: Bug
          Components: jobtracker
            Reporter: Amar Kamat


Consider the following scenario 
# EagerTaskInitializer calls jobtracker.initJob(obj1)
# initJob will snapshot the job run-state to PREP
# Before initJob() issues job1.initTask(), user issues a kill and the job now moves to KILLED state. The jobtracker updates the listener about the PREP->KILLED event.
# Now initJob() issues a job1.initTask() which comes out nicely.
# initJob() now snapshots the job state it will be KILLED
# jobtracker now updates the listener with PREP->KILLED event which is incorrect

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