hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Billie Rinaldi (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-6716) Native services support for specifying component start order
Date Mon, 19 Jun 2017 21:08:00 GMT

     [ 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.002.patch

Added a test and fixed some checkstyle issues.

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

To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org

View raw message