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/23 21:31:40 UTC

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

     [ https://issues.apache.org/jira/browse/MAPREDUCE-758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Allen Wittenauer resolved MAPREDUCE-758.
----------------------------------------

    Resolution: Incomplete

Closing as stale.

> 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 was sent by Atlassian JIRA
(v6.2#6252)