You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Billie Rinaldi (JIRA)" <ji...@apache.org> on 2017/06/16 19:19:00 UTC

[jira] [Created] (YARN-6716) Native services support for specifying component start order

Billie Rinaldi created YARN-6716:
------------------------------------

             Summary: 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


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-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org