hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sangjin Lee (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-2928) Application Timeline Server (ATS) next gen: phase 1
Date Sat, 07 Feb 2015 00:23:39 GMT

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

Sangjin Lee commented on YARN-2928:
-----------------------------------

bq. When you say user, what does it really imply? User "a" can submit a hive query. A tez
application running as user "hive" can execute the query submitted by user "a" using a's delegation
tokens. With proxy users and potential use of delegation tokens, which "user" should be used?

That's something we haven't fully considered. IMO the user is used for resource attribution
(e.g. chargeback) and also for access control. We'll need to sort out this scenario (probably
not for the first cut however).

bq. What are the main differences between meta-data and configuration?

One could argue they are not different. However, from a user's perspective (especially MR
jobs), the configuration has a strong meaning. It might be good to call out configuration
separately from other metadata.

> Application Timeline Server (ATS) next gen: phase 1
> ---------------------------------------------------
>
>                 Key: YARN-2928
>                 URL: https://issues.apache.org/jira/browse/YARN-2928
>             Project: Hadoop YARN
>          Issue Type: New Feature
>          Components: timelineserver
>            Reporter: Sangjin Lee
>            Priority: Critical
>         Attachments: ATSv2.rev1.pdf, ATSv2.rev2.pdf, Data model proposal v1.pdf
>
>
> We have the application timeline server implemented in yarn per YARN-1530 and YARN-321.
Although it is a great feature, we have recognized several critical issues and features that
need to be addressed.
> This JIRA proposes the design and implementation changes to address those. This is phase
1 of this effort.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message