这是最有可能通过SSH花费很长的时间来启动的情况下，造成120秒超时到期前的机器可以登录到造成的。您应该能够运行

This is most likely caused by SSH taking a long time to start up on the instances, causing the 120 second timeout to expire before the machines could be logged into. You should be able to run

./spark-ec2 -i ~/.ssh/myspark.pem -r us-east-1  -k myspark --copy launch --resume try1

（用 - 简历标记），从那里的东西留下来，而无需重新启动新的实例继续。这个问题将在星火1.2.0，在那里我们有智能检查SSH状态，而不是依赖于一个固定的超时的新机制。我们正在通过建设新的AMI也解决了长期SSH启动延迟背后的根本原因。

(with the --resume flag) to continue from where things left off without re-launching new instances. This issue will be fixed in Spark 1.2.0, where we have a new mechanism that intelligently checks the SSH status rather than relying on a fixed timeout. We're also addressing the root causes behind the long SSH startup delay by building new AMIs.