hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vrushali C (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-6734) Ensure sub-application user is extracted & sent to timeline service
Date Wed, 26 Jul 2017 19:17:00 GMT

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

Vrushali C commented on YARN-6734:

Patch v003 seems fine over all. 

I was wondering if we might to pass in the entire callerUgi object in  TimelineCollector.java
L159 instead of just the short name. That way, going forward, for authentication, we would
have all the information that we would need and the API does not have to change. 

What do you think? 

> 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
>         Attachments: YARN-6734-YARN-5355.001.patch, YARN-6734-YARN-5355.002.patch, YARN-6734-YARN-5355.003.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

To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org

View raw message