You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Sangjin Lee (JIRA)" <ji...@apache.org> on 2015/01/17 01:30:35 UTC
[jira] [Updated] (YARN-3030) set up ATS writer with basic request
serving structure and lifecycle
[ https://issues.apache.org/jira/browse/YARN-3030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sangjin Lee updated YARN-3030:
------------------------------
Attachment: YARN-3030.001.patch
Posted patch v.1.
(1)
It sets up the basic skeleton of the aggregator service hierarchy. BaseAggregatorService sets up a core aggregator service. AppLevelAggregatorService is an extension that is instantiated per app.
(2)
I added a partial implementation of the PerNodeAggregator. It serves as a REST end point, and provides lifecycle methods so per-app in-memory aggregators can be created and destroyed according to the app lifecycle.
(3)
Added a few unit tests, and cleaned up the pom a little bit.
This is still a skeleton. I simply used the existing common APIs from ATS to fill in the arguments and so on. We'll need to add more as our APIs jell.
> 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
> Attachments: YARN-3030.001.patch
>
>
> 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)