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-3030) set up ATS writer with basic request serving structure and lifecycle
Date Fri, 16 Jan 2015 01:43:35 GMT

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

Zhijie Shen commented on YARN-3030:
-----------------------------------

bq. work out the timeline client API (both sync and async)

I'm wondering if we have to finalize the data model, such as entities, events and metrics
first, because the APIs are going to operate on these stuff right.

bq. Do we want to use REST similarly, or do we want to consider using RPC?

I suggest going on with REST now, as we may easily reuse existing REST communication stack,
but we can isolate the client/server interface and the underlying communication layer. And
in the future, if we want to take advantage of the operation flexibility of RPC, we can implement
the interface with protos and replace the REST one.

> 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