[
https://issues.apache.org/jira/browse/YARN-3047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14382866#comment-14382866
]
Li Lu commented on YARN-3047:
-----------------------------
Hi [~varun_saxena], thanks for the doc! I have two general questions about your
proposed plan:
# I'm a little bit confused on "Timeline Reader will be a single daemon(in the
initial phase)". In reader overview section there are multiple threads in the
reader, are those threads managed in YARN-3047? Specifically, what is the
concrete plan for "Phase 1" on reader's architecture, single daemon multiple
thread, or single daemon single thread? If it's the former, you may want to
update YARN-3047's patch, while if it's the latter, you may want to confirm
this and update the figure afterwards (not the top priority for now).
# On storage layer we're prioritizing timeline entities and metrics, it would
be great if there are some API support from reader level for metrics. For the
current progress on the storage layer, I'm not sure if we can finish V1 storage
support by the time you finish reader phase 1. We may probably need some
coordination on 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
> Reporter: Sangjin Lee
> Assignee: Varun Saxena
> Attachments: Timeline_Reader(draft).pdf, YARN-3047.001.patch,
> YARN-3047.003.patch, YARN-3047.005.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)
