[
https://issues.apache.org/jira/browse/MAPREDUCE-3432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran moved HADOOP-7839 to MAPREDUCE-3432:
---------------------------------------------------
Component/s: (was: scripts)
mrv2
Affects Version/s: (was: 0.23.0)
0.23.0
Key: MAPREDUCE-3432 (was: HADOOP-7839)
Project: Hadoop Map/Reduce (was: Hadoop Common)
> Yarn doesn't work if JAVA_HOME isn't set
> ----------------------------------------
>
> Key: MAPREDUCE-3432
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3432
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: 0.23.0
> Environment: OS/X, JAVA_HOME unset
> Reporter: Steve Loughran
> Priority: Minor
>
> libexec/hadoop-config.sh does reliably work out JAVA_HOME for many platforms.
> unfortunately, the yarn scripts don't use it. As such you get told off when
> you try to run yarn
> {code}
> $ bin/yarn resourcemanager
> Error: JAVA_HOME is not set.
> {code}
> To make things more interesting, if you set the value in the shell, it still
> doesn't propagate down to the scripts
> {code}
> $ echo $JAVA_HOME
> $ source libexec/hadoop-config.sh
> $ echo $JAVA_HOME
> /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
> $ bin/yarn resourcemanager
> Error: JAVA_HOME is not set.
> $echo $JAVA_HOME
> /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
