[
https://issues.apache.org/jira/browse/YARN-1179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13764278#comment-13764278
]
Jason Lowe commented on YARN-1179:
----------------------------------
Doesn't {{$PWD}} already expand to the current working directory of the
container? MRApps.setClasspath is relying on this to pick up items in the
container working directory for the classpath and
TaskAttemptImpl.createCommonContainerLaunchContext is using it to setup
LD_LIBRARY_PATH appropriately.
> add ApplicationConstants option to define base dir of the installed
> application
> -------------------------------------------------------------------------------
>
> Key: YARN-1179
> URL: https://issues.apache.org/jira/browse/YARN-1179
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: nodemanager
> Affects Versions: 2.1.0-beta
> Reporter: Steve Loughran
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> There is no expanded env variable for the directory into which the NM copies
> down local resources and executes the supplied command(s). This prevents you
> creating environment variables in the context that set absolute paths
> {code}
> env.put("CONF_DIR",absolute path to "/conf")
> {code}
> This could be determined by resolving "." to an absolute value in bash
> scripts, but it would be easier and safer if we just had an auto-expanding
> env variable
> {code}
> env.put("CONF_DIR","<INSTALL_DIR>/conf")
> {code}
> And of course {{INSTALL_DIR}} would be declared in {{ApplicationConstants}}.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
