Varun Saxena commented on YARN-3047:

bq. 1. We should be able to reuse "TimelineAbout".
Ok. Didnt notice this one.

bq. 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 
I dont know about this either. Can you point to the JIRA this discussion took 
place on ? And if there is any conclusion on this.

bq. 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?
We have to do it with webservices. I was thinking of handling this part of 
another JIRA. Because this is just an initial JIRA and we have already started 
the webserver here. Current webapp implementations in YARN use Guice which as 
per new implementation of starting webserver we do not want(because of issue 
which was fixed in YARN-3087). So I will have to explore a bit on that. Hence, 
thought of raising a new JIRA once I work on it. I do not think we are planning 
to launch the reader from another daemon unlike node collector but if we do it 
ever, we can't use Guice from what I could gather from discussion on YARN-3087

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