You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-dev@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2014/04/10 12:26:16 UTC

[jira] [Resolved] (YARN-1554) add an env variable for the YARN AM classpath

     [ https://issues.apache.org/jira/browse/YARN-1554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steve Loughran resolved YARN-1554.
----------------------------------

    Resolution: Duplicate

> 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
(v6.2#6252)