Zhijie Shen commented on YARN-3047:

[~varun_saxena], thanks for working on this issue, and sorry for responding you 
later in this thread. I propose to do the following this jira:

TimelineWebServer: the main entrance of the single-node server that serves 
users' queries.

* TimelineWebServices: It describe the endpoint of the REST APIs. 
TimelineWebServer starts it to intake the HTTP requests. Please refer to 
TimelineAggregatorWebService and TimelineAggregatorsCollection for the new way 
to start the webapp. For now, let's keep the three APIs as we have for ATS v1.
* TimelineDataManager: TimelineWebServices routes the request to 
TimelineDataManager, which is the center place to process the request, 
authorize the access and fetch the data from backend storage.
** TimelineReader: The abstraction of accessing the backend storage. 
TimelineDataManager should instantiate the implementation of TimelineReader, 
and call it to fetch data. TimelineReader should operate on the new data model. 
Some query parameters, such as primaryFilter, may no longer make sense. Again 
let's start with three APIs as we have for ATS v1.
* Script: add commands in shell script to start the new timeline server that 
serves user queries.

Please let me know if it makes sense. I'll go on to review the patch.

> [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: YARN-3047.001.patch, YARN-3047.02.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