[StarCluster] Star cluster not creating instances on Amazon's East Region

[ramit.bhardwaj@sicadinc.com]

 Thanks for prompt reply Justin. I really appreciate it. I'll get back 
 to you with my findings/comments.

 Best Regards
 Ramit

 On Tue, 31 Jul 2012 13:46:37 -0400, Justin Riley <jtriley at MIT.EDU> 
 wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi Ramit,
>
> That error comes directly from AWS.
>
> In the case that you don't specify an availability zone in your
> cluster config StarCluster first launches the master node, then
> determines which zone Amazon chose *within* the us-east-1 region for
> the master, and then launches the rest of the nodes using that zone 
> in
> order to improve cluster locality. Sometimes if the zone is
> overloaded, as you encountered, the request to start the nodes fails.
>
> If you're using external EBS volumes with your cluster then you're
> implicitly specifying an availability zone given that volumes can 
> only
> be attached to instances within their zone and thus StarCluster must
> pick the volume's availability zone as the zone for the entire 
> cluster.
>
> I think it's clear now that we should have an optional flag that
> disables trying to launch all instances within the same zone and
> simply lets Amazon pick the zone for each node (except for master in
> case of EBS volumes). If folks have opinions on this I'd be happy to
> hear them...
>
> For the time being, if you're not using external EBS volumes then you
> can specify the zone to use when launching a cluster:
>
> $ starcluster start -a us-east-1a mycluster
>
> Otherwise if you're using external EBS volumes you will need to
> snapshot your volume and recreate it in another zone that's available
> in order for StarCluster to launch the instances in an alternate 
> zone...
>
> HTH,
>
> ~Justin
>
> On 07/31/2012 01:20 PM, Erik Gafni wrote:
>> It looks like that AWS region is at capacity and physically out of
>> those instance types.  Either try different instance types or
>> switch regions.
>>
>> On Tue, Jul 31, 2012 at 4:58 AM, Ramit Bhardwaj
>> <ramit.bhardwaj at sicadinc.com <mailto:ramit.bhardwaj at sicadinc.com>>
>> wrote:
>>
>> Hello,
>>
>> We are using 'Star cluster' for creating clusters on Amazon Cloud.
>> But off late, we are seeing the following error in our logs when we
>> try to create a cluster on the US-East region:
>>
>> "!!! ERROR - Unsupported: The requested Availability Zone is
>> currently constrained and we are no longer accepting new customer
>> requests for t1/m1/c1/m2 instance types. Please retry your request
>> by not specifying an Availability Zone or choosing us-east-1a,
>> us-east-1d, us-east-1c."
>>
>> Is there anything that we are missing here? The exact setup was
>> working perfectly till last month. We are seeing this problem since
>> last one month.
>>
>> Also, in the forums i did not see anyone reporting this issue. Are
>> there any changes to any policy or something? Please advice.
>>
>> Best Regards Ramit _______________________________________________
>> StarCluster mailing list StarCluster at mit.edu
>> <mailto:StarCluster at mit.edu>
>> http://mailman.mit.edu/mailman/listinfo/starcluster
>>
>>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.19 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAlAYGf0ACgkQ4llAkMfDcrmhkACeLNvrLUPsEWOpIX98E8r2rt6m
> MkEAn2LlTsgjJ1iSrPkRiwgKXzciIpPb
> =IDiw
> -----END PGP SIGNATURE-----