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-6733) Add table for storing sub-application entities
Date Mon, 17 Jul 2017 18:33:00 GMT

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

Vrushali C commented on YARN-6733:
----------------------------------

bq. can you update subapplication row and column schema java doc. Looking into java, I initially
thought column families does not have related and isRelated entities. Looking into implementation
I found these are added!!

I will update the documentation..

bq. In SubApplicationRowKey, subAppUserId -> doAsUser? Where ever sugAppUserId, can you
replace with doAsUser? The reason, the same will be using for offline collector also. Thought
it is internal implementation, better lets use doAsUserId.
Actually, do you recollect, we all discussed this. Although the internal implementation right
now is doAsUser in yarn, the concept is for sub-application user. Hence the name in timeline
service is subAppUserId. Would like to keep it as subAppUserId if that's ok, but I can call
out that subAppUserId is usually doAsUser in yarn in the comments/documentation. 





> Add table for storing sub-application entities
> ----------------------------------------------
>
>                 Key: YARN-6733
>                 URL: https://issues.apache.org/jira/browse/YARN-6733
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>            Reporter: Vrushali C
>            Assignee: Vrushali C
>         Attachments: IMG_7040.JPG, YARN-6733-YARN-5355.001.patch, YARN-6733-YARN-5355.002.patch,
YARN-6733-YARN-5355.003.patch, YARN-6733-YARN-5355.004.patch
>
>
> After a discussion with Tez folks, we have been thinking over introducing a table to
store  sub-application information.
> 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. 
> This jira tracks the code changes needed for  table schema creation.
> I will file other jiras for writing to that table, updating the user name fields to include
sub-application user etc.



--
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


Mime
View raw message