[
https://issues.apache.org/jira/browse/YARN-3047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14380495#comment-14380495
]
Vinod Kumar Vavilapalli commented on YARN-3047:
-----------------------------------------------
Tx for the doc.
Re Multiple options to determine whether an app is active: NMs informing the
readers is backwards to me, though it is proactive. We can just have readers
talk to RM. We can further optimize the calls by letting the readers
asynchronously talk to RM to maintain an in-memory cache of a limited number of
applications that finished say in the last one hour - this should work given
the locality of queries w.r.t time.
> [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
> Reporter: Sangjin Lee
> Assignee: Varun Saxena
> Attachments: Timeline_Reader(draft).pdf, YARN-3047.001.patch,
> YARN-3047.003.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
(v6.3.4#6332)
