If you are explicitly specifying the AMI in your invocation of spark-ec2, may I suggest simply removing any explicit mention of AMI from your invocation? spark-ec2 automatically selects an appropriate AMI based on the specified instance type.
2014년 6월 1일 일요일, Nicholas Chammas<nicholas.cham...@gmail.com>님이 작성한 메시지: > Could you post how exactly you are invoking spark-ec2? And are you having > trouble just with r3 instances, or with any instance type? > > 2014년 6월 1일 일요일, Jeremy Lee<unorthodox.engine...@gmail.com > <javascript:_e(%7B%7D,'cvml','unorthodox.engine...@gmail.com');>>님이 작성한 > 메시지: > > It's been another day of spinning up dead clusters... > > I thought I'd finally worked out what everyone else knew - don't use the > default AMI - but I've now run through all of the "official" quick-start > linux releases and I'm none the wiser: > > Amazon Linux AMI 2014.03.1 - ami-7aba833f (64-bit) > Provisions servers, connects, installs, but the webserver on the master > will not start > > Red Hat Enterprise Linux 6.5 (HVM) - ami-5cdce419 > Spot instance requests are not supported for this AMI. > > SuSE Linux Enterprise Server 11 sp3 (HVM) - ami-1a88bb5f > Not tested - costs 10x more for spot instances, not economically viable. > > Ubuntu Server 14.04 LTS (HVM) - ami-f64f77b3 > Provisions servers, but "git" is not pre-installed, so the cluster setup > fails. > > Amazon Linux AMI (HVM) 2014.03.1 - ami-5aba831f > Provisions servers, but "git" is not pre-installed, so the cluster setup > fails. > >
