[
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.003.patch
Posted patch v.3.
Corrected the issue of using wrong lifecycle methods to initialize/remove app
level services. Also added the web server to be able to serve requests.
The server works fine in a standalone process. However, as an aux service to
the NM, the services comes up and initializes cleanly, but there are issues
serving REST requests. I filed YARN-3087 for that problem.
{color:green}+1 overall{color}.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 4 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version ) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
> 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, YARN-3030.002.patch,
> YARN-3030.003.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)
