Hitesh Shah commented on YARN-2928:

Some questions on the design doc: 

bq. The AM and the ATS writer are always considered as a pair, both in terms of 
resource allocation and failure handling.
Why is this necessary? Why does the ATS layer decide what is fatal or non-fatal 
for an application? 

>From a Tez perspective, we have a different use-case when it comes to 
>relationships with higher level applications. A single tez application can run 
>multiple different Hive queries submitted by different users. In today's 
>implementation, the data generated from each different query ( within the same 
>Tez yarn application ) will have different access/privacy controls. How do you 
>see the flow relationship being handled in this case as there is an entity ( 
>Tez DAG ) that is a child of both a Tez Application as well as a Hive query? 

> 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
>            Assignee: Vinod Kumar Vavilapalli
>            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

Reply via email to