hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-679) add an entry point that can start any Yarn service
Date Fri, 06 Jun 2014 16:22:02 GMT

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

Hadoop QA commented on YARN-679:
--------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12648651/org.apache.hadoop.servic...mon%203.0.0-SNAPSHOT%20API%29.pdf
  against trunk revision .

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-YARN-Build/3919//console

This message is automatically generated.

> add an entry point that can start any Yarn service
> --------------------------------------------------
>
>                 Key: YARN-679
>                 URL: https://issues.apache.org/jira/browse/YARN-679
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: api
>    Affects Versions: 2.4.0
>            Reporter: Steve Loughran
>            Assignee: Steve Loughran
>         Attachments: YARN-679-001.patch, YARN-679-002.patch, org.apache.hadoop.servic...mon
3.0.0-SNAPSHOT API).pdf
>
>
> There's no need to write separate .main classes for every Yarn service, given that the
startup mechanism should be identical: create, init, start, wait for stopped -with an interrupt
handler to trigger a clean shutdown on a control-c interrrupt.
> Provide one that takes any classname, and a list of config files/options



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message