hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zhijie Shen (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (YARN-3047) [Data Serving] Set up ATS reader with basic request serving structure and lifecycle
Date Mon, 29 Jun 2015 23:02:04 GMT

    [ https://issues.apache.org/jira/browse/YARN-3047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14606611#comment-14606611
] 

Zhijie Shen edited comment on YARN-3047 at 6/29/15 11:01 PM:
-------------------------------------------------------------

1. We should be able to reuse "TimelineAbout".

2. I didn't see the web app module in the patch. Do we consider install the web UI on the
reader instance together with web services? Web UI has two forms in ATS v1. One is like generic
history web UI, which is hosted side-by-side with the web services in timeline server, and
which reads the data from the backend directly. The other is like Tez web UI, which is actually
the consumer of the web services/timeline server.

3. Not sure if we have already clarified it or not, but I remember we have some offline discussion
on where to trigger the HBase coprocessor (for aggregation purpose), and it was said to use
reader instance as the central point. We should think of it when constructing the reader stack
too. 


was (Author: zjshen):
1. We should be able to reuse "TimelineAbout".

2. I didn't see the web app module in the patch. Do we consider install the web UI on the
reader instance together with web services? Web UI has two forms in ATS v1. One is like generic
history web UI, which is hosted side-by-side with the web services in timeline server, and
which reads the data from the backend directly. The other is like Tez web UI, which is actually
the consumer of the web services/timeline server.

3. Not sure if we have already clarified it or not, but I remember we have some offline discussion
on where to trigger the HBase coprocessor, and it was said to use reader instance as the central
point. We should think of it when constructing the reader stack too. 

> [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.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
(v6.3.4#6332)

Mime
View raw message