[jira] [Commented] (HADOOP-7839) Yarn doesn't work if JAVA_HOME isn't set

["Steve Loughran (Commented) (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HADOOP-7839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13152918#comment-13152918 ] 

Steve Loughran commented on HADOOP-7839:
----------------------------------------

the workaround is to set it in your .profile file. Having it set in the shell you invoke yarn from is not sufficient. 
                
> Yarn doesn't work if JAVA_HOME isn't set
> ----------------------------------------
>
>                 Key: HADOOP-7839
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7839
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: scripts
>    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