On Thu, Jun 26, 2014 at 9:42 PM, Nicholas Chammas < [email protected]> wrote:
> > That’s technically true, but I’d be surprised if there wasn’t a lot of > room for improvement in spark-ec2 regarding cluster launch+config times. > Unfortunately, this is a spark support issue, but an AWS one. Starting a few months ago, Amazon AWS services have been having bigger and bigger lags. Indeed, the default timeout hard coded in spark-ec2 is no longer able to launch the cluster successfully, and many people here reported that they had to increase it. >
