You are viewing a plain text version of this content. The canonical link for it is here.

Posted to yarn-issues@hadoop.apache.org by "Sunil G (JIRA)" <ji...@apache.org> on 2015/09/10 20:56:46 UTC

[jira] [Commented] (YARN-4142) add a way for an attempt to report an attempt failure

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

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

Hi [~steve_l]
I have a doubt here. In NodeManager {{ContainerImpl}}, we set  diagnostics and exitcode for few error cases. So here  "application explicitly terminates an attempt" means AM kills by itself for some reasons, or AM container/attempt is killed by cli command.

> 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)