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 "Varun Saxena (JIRA)" <ji...@apache.org> on 2017/10/21 06:06:48 UTC
[jira] [Updated] (YARN-6734) Ensure sub-application user is
extracted & sent to timeline service
[ https://issues.apache.org/jira/browse/YARN-6734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Varun Saxena updated YARN-6734:
-------------------------------
Fix Version/s: 2.9.0
> Ensure sub-application user is extracted & sent to timeline service
> -------------------------------------------------------------------
>
> Key: YARN-6734
> URL: https://issues.apache.org/jira/browse/YARN-6734
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: timelineserver
> Reporter: Vrushali C
> Assignee: Rohith Sharma K S
> Labels: atsv2-subapp
> Fix For: 2.9.0, YARN-5355, 3.0.0-beta1, YARN-5355-branch-2
>
> Attachments: YARN-6734-YARN-5355.001.patch, YARN-6734-YARN-5355.002.patch, YARN-6734-YARN-5355.003.patch, YARN-6734-YARN-5355.004.patch
>
>
> After a discussion with Tez folks, we have been thinking over introducing a table to store sub-application information. YARN-6733
> For example, if a Tez session runs for a certain period as User X and runs a few AMs. These AMs accept DAGs from other users. Tez will execute these dags with a doAs user. ATSv2 should store this information in a new table perhaps called as "sub_application" table.
> YARN-6733 tracks the code changes needed for table schema creation.
> This jira tracks writing to that table, updating the user name fields to include sub-application user etc. This would mean adding a field to Flow Context which can store an additional user
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org