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

Sangjin Lee commented on YARN-3047:
-----------------------------------

The main reason for going directly to the per-app timeline collector in the 
original design was to get the up-to-date view of the data. Having said that, I 
believe in subsequent discussions we felt that it was acceptable to have a 
somewhat stale view if it is due to data being flushed with some interval.

I am fine with moving ahead without talking to the timeline collector directly. 
If later we deem that the view is too stale and we need to get the more recent 
data from the timeline collector, we could add that functionality in a separate 
effort.

> [Data Serving] Set up ATS reader with basic request serving structure and 
> lifecycle
> -----------------------------------------------------------------------------------
>
>                 Key: YARN-3047
>                 URL: https://issues.apache.org/jira/browse/YARN-3047
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>            Reporter: Sangjin Lee
>            Assignee: Varun Saxena
>         Attachments: Timeline_Reader(draft).pdf, YARN-3047.001.patch, 
> YARN-3047.003.patch, YARN-3047.02.patch, YARN-3047.04.patch
>
>
> Per design in YARN-2938, set up the ATS reader as a service and implement the 
> basic structure as a service. It includes lifecycle management, request 
> serving, and so on.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to