[
https://issues.apache.org/jira/browse/YARN-2928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14315665#comment-14315665
]
Zhijie Shen commented on YARN-2928:
-----------------------------------
bq. I am assuming you are already aware of YARN-2423 and plan to maintain
compatibility
The data models of current and next gen TS are likely to be different. To be
compatible to old data model, we probably need to change the existing timeline
client to covert the old entity to the new one.
bq. We should have such a configuration that disables the timeline service
globally.
I think it's also good to have per-app flag. If the app is configured not to
use the timeline service, we don't need to start the per-app aggregator.
bq. My point related to events was not about a new interesting feature but to
generally understand what use case is meant to be solved by events and how
should an application developer use events?
I thought you mean using publisher/subscriber architecture, such as Kafka, to
consume the incoming event streams. Other than that, IMHO, we still need to
support the existing query of getting the stored events of a set of some
entities.
> 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: 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)
