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

Vrushali C commented on MAPREDUCE-5502:
---------------------------------------


Thanks [~jlowe] for the pointer to the bug MAPREDUCE-5497 . 

>From our investigation, it appears that the client's kill sends a KILL to the 
>App Master as well as to the RM for this App. The kill signal to RM was 
>getting processed earlier than AM's call of unregistering with history url 
>update etc.

Similar to the patch in MAPREDUCE-5497, in YarnRunner's killJob function, we 
added a sleep for a few seconds before the (2nd) call to 
resMgrDelegate.killApplication where status.getState() != 
JobStatus.State.KILLED. That seems to have fixed this race condition. 

What do you think? 

Backporting the above patch needs some work since 
org.apache.hadoop.service.Service does not exist in 2.0.5. 
                
> History link in resource manager is broken for KILLED jobs
> ----------------------------------------------------------
>
>                 Key: MAPREDUCE-5502
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5502
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: resourcemanager
>    Affects Versions: 2.0.5-alpha
>            Reporter: Vrushali C
>            Assignee: Vrushali C
>              Labels: ui
>
> History link in resource manager is broken for KILLED jobs.
> Seems to happen with jobs with State 'KILLED' and FinalStatus 'KILLED'. If 
> the State is 'FINISHED' and FinalStatus is 'KILLED', then the "History" link 
> is fine.
> It isn't easy to reproduce the problem since the time at which the app is 
> killed determines the state it ends up in, which is hard to guess. these 
> particular jobs seem to get a Diagnostics message of "Application killed by 
> user." where as the other killed jobs get " Kill Job received from client 
> job_1378766187901_0002
> Job received Kill while in RUNNING state. "

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to