Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 19 Jul 2016 11:04:20 +0000 (UTC)
From: "Steve Loughran (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12647412.1368489598000.70894.1468926260673@Atlassian.JIRA>
In-Reply-To: <JIRA.12647412.1368489598000@Atlassian.JIRA>
References: <JIRA.12647412.1368489598000@Atlassian.JIRA> <JIRA.12647412.1368489598145@arcas>
Subject: [jira] [Updated] (YARN-679) add an entry point that can start any
 Yarn service
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 19 Jul 2016 11:04:22 -0000


     [ https://issues.apache.org/jira/browse/YARN-679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steve Loughran updated YARN-679:
--------------------------------
    Attachment: YARN-679-009.patch

Patch 009, synced up with trunk

HADOOP-13179 broke things, as it made the building of common options private/static, not, as I needed for some things, subclassable. I fixed by making that protected and synchronized on {{OptionBuilder}}, which is what everything should do.

[~aw] I've edited references to the PR in the JIRA. Will patches now take, or is there some secret DB I need to alter?

> 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: New Feature
>          Components: api
>    Affects Versions: 2.8.0
>            Reporter: Steve Loughran
>            Assignee: Steve Loughran
>         Attachments: YARN-679-001.patch, YARN-679-002.patch, YARN-679-002.patch, YARN-679-003.patch, YARN-679-004.patch, YARN-679-005.patch, YARN-679-006.patch, YARN-679-007.patch, YARN-679-008.patch, YARN-679-009.patch, org.apache.hadoop.servic...mon 3.0.0-SNAPSHOT API).pdf
>
>          Time Spent: 72h
>  Remaining Estimate: 0h
>
> 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 interrupt.
> Provide one that takes any classname, and a list of config files/options


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org