Vinod Kumar Vavilapalli commented on YARN-2928:

bq. The AM and the ATS writer are always considered as a pair, both in terms of 
resource allocation and failure handling.
bq. Why is this necessary? Why does the ATS layer decide what is fatal or 
non-fatal for an application? 
This might have meant something different. Colocating the AM and the Timeline 
aggregator is a physical optimization that also simplifies scheduling a bit. So 
if the AM fails and runs on a different host, it may make sense to move the 
aggregator too.

> 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

Reply via email to