I also found this issue. I have reported it as a bug
https://issues.apache.org/jira/browse/SPARK-5242 and submitted a fix. You
can find link to fixed fork in the comments on the issue page. Please vote
on the issue, hopefully guys will accept pull request faster then :)
Regards, Vladimir
On Mon,
I running the master branch.
Finally I can make it work, changing all occurrences of "*public_dns_name*"
property with "*private_ip_address*" in the spark_ec2.py script.
My VPC instances always have null value in "*public_dns_name*" property
Now my script only work for VPC instances.
Regards
E
What version of the script are you running? What did you see in the EC2 web
console when this happened?
Sometimes instances just don't come up in a reasonable amount of time and
you have to kill and restart the process.
Does this always happen, or was it just once?
Nick
On Thu, Dec 18, 2014 at
Hi guys.
I run the folling command to lauch a new cluster :
./spark-ec2 -k test -i test.pem -s 1 --vpc-id vpc-X --subnet-id
subnet-X launch vpc_spark
The instances started ok but the command never end. With the following
output:
Setting up security groups...
Searching for existing cl
