hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sangjin Lee (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3030) set up ATS writer with basic request serving structure and lifecycle
Date Fri, 16 Jan 2015 02:09:35 GMT

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

Sangjin Lee commented on YARN-3030:
-----------------------------------

You're right. We need the object model to be able to hash out the client API fully. Here I
was suggesting putting a skeleton in (mostly empty classes for the object model). We'll have
to come back to it as we work on the object model.

I'm OK with going with REST for now. We'll need to get quick consensus on the code/package
organization however (see https://issues.apache.org/jira/browse/YARN-2928?focusedCommentId=14279655&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14279655).

> set up ATS writer with basic request serving structure and lifecycle
> --------------------------------------------------------------------
>
>                 Key: YARN-3030
>                 URL: https://issues.apache.org/jira/browse/YARN-3030
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>            Reporter: Sangjin Lee
>            Assignee: Sangjin Lee
>
> Per design in YARN-2928, create an ATS writer as a service, and implement the basic service
structure including the lifecycle management.
> Also, as part of this JIRA, we should come up with the ATS client API for sending requests
to this ATS writer.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message