Thanks. Turns out this is a proxy problem somehow. Sorry to bother you.
/Håkan
On Mon Jan 26 2015 at 11:02:18 AM Franc Carter franc.car...@rozettatech.com
wrote:
AMI's are specific to an AWS region, so the ami-id of the spark AMI in
us-west will be different if it exists. I can't remember
AMI's are specific to an AWS region, so the ami-id of the spark AMI in
us-west will be different if it exists. I can't remember where but I have a
memory of seeing somewhere that the AMI was only in us-east
cheers
On Mon, Jan 26, 2015 at 8:47 PM, Håkan Jonsson haj...@gmail.com wrote:
Thanks,
Thanks,
I also use Spark 1.2 with prebuilt for Hadoop 2.4. I launch both 1.1 and
1.2 with the same command:
./spark-ec2 -k foo -i bar.pem launch mycluster
By default this launches in us-east-1. I tried changing the the region
using:
-r us-west-1 but that had the same result:
Could not resolve
I definitely have Spark 1.2 running within EC2 using the spark-ec2 scripts.
I downloaded Spark 1.2 with prebuilt for Hadoop 2.4 and later.
What parameters are you using when you execute spark-ec2?
I am launching in the us-west-1 region (ami-7a320f3f) which may explain
things.
On Mon Jan 26 2015
Hi,
When I try to launch a standalone cluster on EC2 using the scripts in the
ec2 directory for Spark 1.2, I get the following error:
Could not resolve AMI at:
https://raw.github.com/mesos/spark-ec2/v4/ami-list/us-east-1/pvm
It seems there is not yet any AMI available on EC2. Any ideas when
