hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Lowe (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-4142) add a way for an attempt to report an attempt failure
Date Fri, 11 Sep 2015 14:47:46 GMT

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

Jason Lowe commented on YARN-4142:

The idea here is to allow applications to update their diagnostics without failing the entire
application.  Currently the only way the app attempt can update its diagnostics is when it
unregisters, and that necessarily means the app is completely done with no further attempts.
 There either needs to be a way to update diagnostics via the allocate heartbeat or the ability
for application attempts to unregister without terminating the overall application.

> 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

View raw message