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

Sunil G commented on YARN-4142:
-------------------------------

Thanks for clarifying [~jlowe] [~steve_l]

If we are adding a diagnostics information in {{AllocateRequest}}, RM can fetch 
any diagnostics which AM wants to report, to RMAppAttempt level. So its also 
possible that different types of diagnostics can be sent by AM if needed (may 
be over various heartbeats before its send unRegister). With this RM must be 
able to store it and associate it with attempt in order of importance if 
possible. 
If AM ensures that all such diagnostics are sent before it calls  
{{finishApplicationMaster}}, I feel this my be a good option.

> add a way for an attempt to report an attempt failure
> -----------------------------------------------------
>
>                 Key: YARN-4142
>                 URL: https://issues.apache.org/jira/browse/YARN-4142
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: api
>    Affects Versions: 2.8.0
>            Reporter: Steve Loughran
>
> Currently AMs can report a failure with exit code and diagnostics text —but 
> only when exiting to a failed state. If the AM terminates for any other 
> reason there's no information held in the RM, just the logs somewhere —and we 
> know they don't always last.
> When an application explicitly terminates an attempt, it would be nice if it 
> could  optionally report something to the RM before it exited. The most 
> recent set of these could then be included in Application Reports, so 
> allowing client apps to count attempt failures and get exit details.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to