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 00:48:35 GMT

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

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

Also, the current ATS timeline client API is based on REST. Do we want to use REST similarly,
or do we want to consider using RPC? The standard pros and cons apply here: REST would be
bit better with off-cluster arbitrary clients, minimize code coupling between client and server,
and make things more symmetric between reads and writes. On the other hand, RPC would provide
more flexibility in terms of operations.

Thoughts?

> 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