Hi Toby, It is usually the case that even if the EC2 console says the nodes are up, they are not really fully initialized. For 16 nodes I have found `--wait 800` to be the norm that makes things work.
In my previous experience I have found this to be the culprit, so if you immediately do 'launch --resume' when you see the first SSH error it's still very likely to fail. But if you wait a little bit longer and do 'launch --resume', it could work. Zongheng On Thu, Jun 12, 2014 at 1:03 PM, Toby Douglass <[email protected]> wrote: > On Thu, Jun 12, 2014 at 8:50 PM, Nicholas Chammas > <[email protected]> wrote: >> >> Yes, you need Python 2.7 to run spark-ec2 and most AMIs come with 2.6 > > Ah, yes - I mean to say, Amazon Linux. >> >> .Have you tried either: >> >> Retrying launch with the --resume option? >> Increasing the value of the --wait option? > > No. I will try the first, now. I think the latter is not the issue - the > instances are up; something else is amiss. > > Thankyou. >
