Sangjin Lee commented on YARN-3047:

2. I didn't see the web app module in the patch. Do we consider install the web 
UI on the reader instance together with web services? Web UI has two forms in 
ATS v1. One is like generic history web UI, which is hosted side-by-side with 
the web services in timeline server, and which reads the data from the backend 
directly. The other is like Tez web UI, which is actually the consumer of the 
web services/timeline server.

The reader generic web UI is definitely something we need, but that is a fairly 
big piece that requires some design. Can we capture that in a separate ticket?

3. Not sure if we have already clarified it or not, but I remember we have some 
offline discussion on where to trigger the HBase coprocessor (for aggregation 
purpose), and it was said to use reader instance as the central point. We 
should think of it when constructing the reader stack too.

Could you kindly give me some context on this? I don't recall under what 
scenarios we were thinking of triggering the co-processor on the *read* path...

> [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
>    Affects Versions: YARN-2928
>            Reporter: Sangjin Lee
>            Assignee: Varun Saxena
>              Labels: BB2015-05-TBR
>         Attachments: Timeline_Reader(draft).pdf, 
> YARN-3047-YARN-2928.08.patch, YARN-3047-YARN-2928.09.patch, 
> YARN-3047.001.patch, YARN-3047.003.patch, YARN-3047.005.patch, 
> YARN-3047.006.patch, YARN-3047.007.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