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

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

bq. In the following, depending on how the writer is implemented, we may want 
to preserve the outstanding timeline data that is received by ATS companion but 
is still not be persisted into the storage backend. IAC, it seem to be the 
common requirement no matter it's per-node (e.g., restarting) or per-app (e.g., 
crashing).

The point taken about the need to recover the in-memory data in either approach.

I am fine with starting with the per-node companion approach with the 
understanding that at some point we need to have at least an option of the 
per-app companion. We can reword YARN-3033 to do that. What do others think? 
[~jrottinghuis]?

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