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

Rohith Sharma K S edited comment on YARN-5599 at 9/19/16 11:09 AM:
-------------------------------------------------------------------

IIUC, the scope of the JIRA is to publish AM launcher artifacts to ATSv2 for 
debugging in case of launch failure. May be issue reporter can make it clear. 
cc:-/[~templedf]
On flip-side, in case of container launch failures YARN already keeps track of 
diagnostics message and also publishes to ATS. 

And regarding security of these data, ATSv2 has to take care which will be 
supported in future.


was (Author: rohithsharma):
IIUC, the scope of the JIRA is to publish AM launcher artifacts to ATSv2 for 
debugging in case of launch failure. May be issue reporter can clear about it.
On flip-side, in case of container launch failures YARN already keeps track of 
diagnostics message and also publishes to ATS. 

And regarding security of these data, ATSv2 has to take care which will be 
supported in future.

> 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

Reply via email to