hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-1554) add an env variable for the YARN AM classpath
Date Thu, 02 Jan 2014 11:05:50 GMT

    [ https://issues.apache.org/jira/browse/YARN-1554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13860131#comment-13860131

Steve Loughran commented on YARN-1554:

As  noted in {{org.apache.hadoop.yarn.applications.distributedshell.Client}}:

    // At some point we should not be required to add 
    // the hadoop specific classpaths to the env. 
    // It should be provided out of the box. 
    // For now setting all required classpaths including
    // the classpath to "." for the application jar

> add an env variable for the YARN AM classpath
> ---------------------------------------------
>                 Key: YARN-1554
>                 URL: https://issues.apache.org/jira/browse/YARN-1554
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: nodemanager
>    Affects Versions: 2.2.0
>            Reporter: Steve Loughran
>            Priority: Minor
> Currently YARN apps set up their classpath via the default value {{YarnConfiguration.DEFAULT_YARN_APPLICATION_CLASSPATH}}
or an overridden property {{yarn.application.classpath}}. 
> If you don't have the classpath right, the AM won't start up. This means the client needs
to be explicitly configured with the CP.
> If the node manager exported the classpath property via an env variable {{YARN_APPLICATION_CLASSPATH}},
then the classpath could be set up in the AM simply by referencing that property, rather than
hoping its setting is in sync. 

This message was sent by Atlassian JIRA

View raw message