[ 
https://issues.apache.org/jira/browse/YARN-4142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sunil G updated YARN-4142:
--------------------------
    Attachment: 0001-YARN-4142.patch

Uploading an initial version of patch.

Few points:
- Used a new configuration for "diagnostics message size"  to ensure that 
memory is in range for diagnostics message per  attempt  level.
- Once size limit is reached, I have cleared the old buffer. This is done for 
simplicity for now, if needed we can use a rolling buffer approach. 
- This new AM diagnostics message is updated to {{ApplicationAttemptReport}}



> 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
>            Assignee: Sunil G
>         Attachments: 0001-YARN-4142.patch
>
>
> 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