[YARN-6716] Native services support for specifying component start order

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: yarn-native-services
• Component/s: yarn-native-services
• Target Version/s: yarn-native-services
• Hadoop Flags: Reviewed
• Assignee: Billie Rinaldi
• Reporter: Billie Rinaldi
• Created: 16/Jun/17 19:18
• Updated: 06/Nov/17 22:33
• Resolved: 27/Jun/17 00:04

Description

Some native services apps have components that should be started after other components. The readiness_check and dependencies features of the native services API are currently unimplemented, and we could use these to implement a basic start order feature. When component B has a dependency on component A, the AM could delay making a container request for component B until component A's readiness check has passed (for all instances of component A).