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

Jason Lowe commented on YARN-4142:
----------------------------------

Sure, as long as there's a limiting mechanism it should be OK to prototype for 
adding diagnostics to heartbeats.  We may also want the ability to unregister 
cleanly yet still launch another attempt which is another way to accomplish the 
original JIRA request, but we can do that separately if needed.  As Steve 
mentioned above, having the ability to update diagnostics while the app is 
running could be useful for scenarios outside of attempt failure.

> 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