[
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-003.patch
Revised patch
# uses reflection to load the HDFS and YARN configurations if present -so
forcing in their resources
# uses {{GenericOptionsParser}} to parse the options -so the command line is
now consistent with ToolRunner. (There's one extra constraint -that all configs
resolve to valid paths in the filesystem)
# {{GenericOptionsParser}} adds a flag to indicate whether or not the parse
worked...until now it looks like an invalid set of generic options could still
get handed down to the tool
> 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,
> YARN-679-002.patch, YARN-679-003.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
> interrrupt.
> Provide one that takes any classname, and a list of config files/options
--
This message was sent by Atlassian JIRA
(v6.2#6252)
