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] [Commented] (YARN-3047) [Data Serving] Set up ATS reader with basic request serving structure and lifecycle
Date Mon, 23 Mar 2015 16:10:12 GMT

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

Zhijie Shen commented on YARN-3047:
-----------------------------------

bq. We can probably move it to yarn-api.

I prefer to keeping it in the server module, unless it's supposed to be public to users.

bq. This has to be discussed though as Zhijie Shen thinks we can use the same v1 config.

My opinion is that collector should bind on a random port, which will be reported to timeline
client. Reader on single daemon should start on a configured port, and users know it form
the config.

bq. TimelineReaderWebServer

If you'd like to keep "reader, I'm fine with it, but let's still say TimelineReaderServer.
Meanwhile, TimelineReaderWebService -> TimelineReaderWebService*s*.

> [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: YARN-3047.001.patch, YARN-3047.003.patch, YARN-3047.02.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