Sparkling Water 1.6 on EC2 fails with "File Not Found"

[exalate-issue-sync[bot]]

I've never had a problem using the old documentation (below) starting up a Spark EC2 cluster using the Spark EC2 script, then SSH'ing in, downloading Sparkling Water, then launching an H2O cloud on the Spark EC2 cluster, but I can't get it to work under the "new" documentation on the website.

Once I have a Spark 1.6.1 cluster running (let's say the master is 12.34.56.78) what is the proper script to launch an H2O cloud? When I try the new script (per the website) or my old one (below) I get a variation of this error (my emphasis):

bin/sparkling-shell: line 22: /root/spark//bin/spark-shell: No such file or directory

So assuming I start up a Spark cluster using the script below, then SSH in, how do I get an H2O cloud running on the Spark cluster?

cd ./spark-1.6.1-bin-hadoop2.4/ec2 

./spark-ec2 \
--key-pair=<key-pair> \
--identity-file=/my/info/file.pem \
--instance-type=r3.large \
-s 1  \
--spot-price=0.25 \
launch spark_h2o_cluster

Old Code Begin

wget http://h2o-release.s3.amazonaws.com/sparkling-water/rel-1.4/10/sparkling-water-1.4.10.zip

unzip sparkling-water-1.4.10.zip

rm sparkling-water-1.4.10.zip

Start Sparkling Water

cd ./sparkling-water-1.4.10/

export SPARK_HOME='/root/spark/'

export MASTER='spark://ec2-12-34-56-78.compute-1.amazonaws.com:7077'

bin/sparkling-shell

import org.apache.spark.h2o. val h2oContext = new H2OContext(sc).start(1) import h2oContext.

Old Code End

--

[exalate-issue-sync[bot]]

Jakub Hava commented: Closing as this is really old. I suggest trying the latest versions where a lot of improvements are available and reporting a new jira if necessary

[exalate-issue-sync[bot]]

Jakub Hava commented: Closing as this is really old. I suggest trying the latest versions where a lot of improvements are available and reporting a new jira if necessary

[DinukaH2O]

JIRA Issue Migration Info

Jira Issue: SW-114 Assignee: UNASSIGNED Reporter: Michal Malohlava State: Closed Fix Version: N/A Attachments: N/A Development PRs: N/A

[hasithjp]

JIRA Issue Migration Info Cont'd

Jira Issue Created Date: 2016-04-08T10:55:55.986-0700