[YARN-679] add an entry point that can start any Yarn service

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.8.0
• Fix Version/s: 2.9.0, 3.0.0-alpha4
• Component/s: api
• Target Version/s: 2.9.0
• Hadoop Flags: Reviewed
• Assignee: Steve Loughran
• Reporter: Steve Loughran
• Created: 13/May/13 23:59
• Updated: 03/May/17 18:45
• Resolved: 28/Apr/17 18:32

Description

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

Issue Links

• breaks: HADOOP-14368 ExitUtil change by YARN-679 breaks HDFS tests
• incorporates: HADOOP-9626 Add an interface for any exception to serve up an Exit code
• is depended upon by: HADOOP-13035 Add states INITING and STARTING to YARN Service model to cover in-transition states.
• is depended upon by: SLIDER-94 Get YARN utility features into yarn-common
• is related to: HADOOP-13179 GenericOptionsParser is not thread-safe because commons-cli OptionBuilder is not thread-safe
• is related to: HADOOP-13391 Make uses of OptionsBuilder synchronized on OptionsBuilder.class
• is related to: YARN-2127 Move YarnUncaughtExceptionHandler into Hadoop common
• relates to: YARN-896 Roll up for long-lived services in YARN
• links to: GitHub Pull Request #68