Sangjin Lee commented on YARN-3047:

bq. My assumption here is that we only care about per-application partial 
order, but not a total order on the timeline server. So I assume there are 
multiple "timelines" on the server, one for each application, but not a global 
timeline (which cost much more). Based on this assumption I think we can focus 
on reading from storage level firstly.

I'm not quite sure what you meant by this. Could you kindly elaborate on the 
"partial order" and the "total order"? Maybe I missed some context.

> [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.005.patch, YARN-3047.006.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

Reply via email to