JAVA_HOME is picked up from the client/deploying machine

[boneill42]

I'm deploying from Mac OS X onto a YARN cluster running on RHEL.
I've tested the YARN cluster with Pig, and all appears to be well.

Storm-Yarn works like a champ, but the logs from the Resource Manager show:
"/Library/Java/JavaVirtualMachines/jdk1.7.0_09.jdk/Contents/Home//bin/java: No such file or directory"

I haven't looked deep enough yet, but it appears to be picking up my JAVA_HOME from the client machine and using that when it exec's on the YARN cluster.
I believe I can hack around it by deploying from a Linux machine, but wanted to make you guys aware.

This is the actual exception shown in the ResourceManager.

Application application_1380078062907_0003 failed 2 times due to AM Container for appattempt_1380078062907_0003_000002 exited with exitCode: 127 due to: Exception from container-launch:
org.apache.hadoop.util.Shell$ExitCodeException:
at org.apache.hadoop.util.Shell.runCommand(Shell.java:458)

[anfeng]

Pull request #52 and #53 have created for this issue.

[boneill42]

Thanks Andy, appreciate the quick fix.

[firmsnail]

It means that we should configure JDK7 on yarn?