[
https://issues.apache.org/jira/browse/YARN-6716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Billie Rinaldi updated YARN-6716:
---------------------------------
Attachment: YARN-6716-yarn-native-services.001.patch
> Native services support for specifying component start order
> ------------------------------------------------------------
>
> Key: YARN-6716
> URL: https://issues.apache.org/jira/browse/YARN-6716
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: yarn-native-services
> Reporter: Billie Rinaldi
> Assignee: Billie Rinaldi
> Attachments: YARN-6716-yarn-native-services.001.patch
>
>
> 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).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
