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

Zhijie Shen commented on MAPREDUCE-5641:
----------------------------------------

ah, sorry I said the wrong word. It should be finished, *failed*, killed. If AM 
crashes, given no more retry, the application will be failed, right. AHS 
records the information from the view of RM.

bq. Please excuse my ignorance about AHS. What is the source of applications 
for the AHS? Does it periodically poll the RM? Or, does the RM trigger 
something on the completion of an app or its attempts?

AHS doesn't query RM. Instead RM pushes the information to a store where AHS 
can read. The information will be pushed  in terms of events before the 
application life cycle gets completed, no matter whether it completes as 
finished, failed or killed.

> History for failed Application Masters should be made available to the Job 
> History Server
> -----------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-5641
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5641
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: applicationmaster, jobhistoryserver
>    Affects Versions: 2.2.0
>            Reporter: Robert Kanter
>            Assignee: Robert Kanter
>         Attachments: MAPREDUCE-5641.patch, MAPREDUCE-5641.patch
>
>
> Currently, the JHS has no information about jobs whose AMs have failed.  This 
> is because the History is written by the AM to the intermediate folder just 
> before finishing, so when it fails for any reason, this information isn't 
> copied there.  However, it is not lost as its in the AM's staging directory.  
> To make the History available in the JHS, all we need to do is have another 
> mechanism to move the History from the staging directory to the intermediate 
> directory.  The AM also writes a "Summary" file before exiting normally, 
> which is also unavailable when the AM fails.  



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Reply via email to