Sangjin Lee commented on YARN-3047:

Thanks for the quick update!

Can we go all the way and simply use TimelineReaderServer, though? You could 
set the configuration to pass in "http://localhost:0";, and add a method in 
TimelineReaderServer to return the actual address. That way, you could really 
use TimelineReaderServer as is, without resorting to directly setting things up 
with HttpServer2. The current code works, but it's potentially not cheap to 
keep it up, as every time we make any changes to that portion of 
TimelineReaderServer, you'd need to remember to make changes to 
TestTimelineReaderWebServices too.

You might want to take a look at NodeTimelineCollectorManager for this.

> [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-YARN-2928.10.patch, YARN-3047-YARN-2928.11.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