hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amar Kamat (JIRA)" <j...@apache.org>
Subject [jira] Commented: (MAPREDUCE-758) JobInProgressListener events might be garbled
Date Wed, 07 Oct 2009 06:20:31 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12762895#action_12762895
] 

Amar Kamat commented on MAPREDUCE-758:
--------------------------------------

Need to check if this is still valid given MAPREDUCE-805.

> 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.


Mime
View raw message