[
https://issues.apache.org/jira/browse/YARN-5599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15506160#comment-15506160
]
Naganarasimha G R commented on YARN-5599:
-----------------------------------------
IMO it would be better to capture it in any version of ATS, as it will help in
analysis.
bq. in case of container launch failures YARN already keeps track of
diagnostics message and also publishes to ATS.
Yes but IIRC it would collect the 4k bytes log message as failure to launch but
may not be the launch command which we are trying to capture here right ?
> Post AM launcher artifacts to ATS
> ---------------------------------
>
> Key: YARN-5599
> URL: https://issues.apache.org/jira/browse/YARN-5599
> Project: Hadoop YARN
> Issue Type: Improvement
> Reporter: Daniel Templeton
> Assignee: Rohith Sharma K S
> Attachments: 0001-YARN-5599.patch
>
>
> To aid in debugging launch failures, it would be valuable to have an
> application's launch script and logs posted to ATS. Because the
> application's command line may contain private credentials or other secure
> information, access to the data in ATS should be restricted to the job owner,
> including the at-rest data.
> Along with making the data available through ATS, the configuration parameter
> introduced in YARN-5549 and the log line that it guards should be removed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
