[
https://issues.apache.org/jira/browse/YARN-6716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16059659#comment-16059659
]
Jian He commented on YARN-6716:
-------------------------------
when we assign priority key to components, I think we may also consider the
dependency order here, the dependent-upon component should have higher
priorities so that its containers get the higher chance to be allocated.
Basically, we may sort the components in dependency order in below code ?
{code}
for (Component component : app.getComponents()) {
priority = getNewPriority(priority);
String name = component.getName();
if (roles.containsKey(name)) {
continue;
}
log.info("Adding component: " + name);
createComponent(name, component, priority++);
}
{code}
> 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,
> YARN-6716-yarn-native-services.002.patch,
> YARN-6716-yarn-native-services.003.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
