Sangjin Lee commented on YARN-3047:

I need to double check the current state of the code, but in principle the 
writer will not depend on the configuration for the end point. The writer 
(collector) is created dynamically on a per-app basis, and its end point is 
registered on the RM. That's how timeline clients discover the end points. So I 
doubt that the configuration is used any longer to define the writer end point 
(correct me if I'm wrong [~zjshen]).

> [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
>         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-YARN-2928.12.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