Sangjin Lee commented on YARN-3047:

We envision having a pool of ATS readers serving client requests. Having said 
that, I recognize that it involves working out how those ATS reader instances 
are load balanced and named via VIP, etc.

Initially I think we can start with a single instance of ATS reader (as a 
daemon), and tackle the problem of addressing and load balancing later.

In either case, the ATS reader should be fully multi-threaded to serve requests.

Hope that answers your questions.

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