spark-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Williams, Ken" <Ken.Willi...@windlogics.com>
Subject Re: JAVA_HOME problem with upgrade to 1.3.0
Date Thu, 19 Mar 2015 16:37:48 GMT

> From: Ted Yu <yuzhihong@gmail.com<mailto:yuzhihong@gmail.com>>
> Date: Thursday, March 19, 2015 at 11:05 AM
>
> JAVA_HOME, an environment variable, should be defined on the node where appattempt_1420225286501_4699_000002
ran.

Has this behavior changed in 1.3.0 since 1.2.1 though?  Using 1.2.1 and making no other changes,
the job completes fine.

I do have JAVA_HOME set in the hadoop config files on all the nodes of the cluster:

    % grep JAVA_HOME /etc/hadoop/conf/*.sh
    /etc/hadoop/conf/hadoop-env.sh:export JAVA_HOME=/usr/jdk64/jdk1.6.0_31
    /etc/hadoop/conf/yarn-env.sh:export JAVA_HOME=/usr/jdk64/jdk1.6.0_31

 -Ken


________________________________

CONFIDENTIALITY NOTICE: This e-mail message is for the sole use of the intended recipient(s)
and may contain confidential and privileged information. Any unauthorized review, use, disclosure
or distribution of any kind is strictly prohibited. If you are not the intended recipient,
please contact the sender via reply e-mail and destroy all copies of the original message.
Thank you.

Mime
View raw message