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

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

bq. What use are events? Will there be a "streaming" API available to listen to 
all events based on some search criteria? If there is a hierarchy of objects, 
will there be support to listen to or retrieve all events for a given tree by 
providing a root node?

That is a good question. In the design doc, I kept the events mainly because it 
is there in ATS today. I envision that the "events" we will support are mostly 
state transitions (e.g. application submitted, container finished, etc.). One 
could argue that it is just an update of an entity state. At minimum we need a 
property that will hold entity state and an update that will change the state 
value.

> 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)

Reply via email to