[
https://issues.apache.org/jira/browse/YARN-2928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14310280#comment-14310280
]
Hitesh Shah commented on YARN-2928:
-----------------------------------
bq. In the per-app timeline aggregator (a.k.a. ATS writer companion) model, it
is a special container. And we need to be able to allocate both the timeline
aggregator and the AM or neither. Also, we do want to be able to co-locate the
AM and the aggregator on the same node.
Does these mean that containers ( non-AM ) of an application will face a
penalty if they need to write data to ATS as all data will need to be routed to
the aggregator on the AM host first?
> 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)
