|
Discussion Forums
|
Thread: InsufficientInstanceCapacity: Insufficient capacity.
 |
This question is not answered.
Helpful answers available: 2.
Correct answers available: 1.
|
|
|
|
Replies:
9
-
Pages:
1
-
Last Post:
Oct 19, 2009 6:16 AM
by: Colin Rhodes
|
|
|
Posts:
4
Registered:
9/29/09
|
|
|
|
InsufficientInstanceCapacity: Insufficient capacity.
Posted:
Oct 5, 2009 9:41 AM PDT
|
|
|
It used to be I'd see this once a month and it would resolve itself within minutes.
I've been trying to launch a server for the last 12 hours and have gotten this error message every time. Last week the same problem persisted for over 7 hours.
Is there anything that can be done other than to wait?
Thanks
|
|
Posts:
112
Registered:
6/22/06
|
|
|
|
Re: InsufficientInstanceCapacity: Insufficient capacity.
Posted:
Oct 6, 2009 12:46 AM PDT
in response to: flippyhead
|
|
|
My apologies for the trouble you are having. What instance type and availability zone have you been requesting? What may help is to try either a different availability zone, or a different instance type.
|
|
Posts:
4
Registered:
9/29/09
|
|
|
|
Re: InsufficientInstanceCapacity: Insufficient capacity.
Posted:
Oct 6, 2009 7:35 AM PDT
in response to: Udjeni
|
|
|
US, m1small and m1 large instances, seems to be effecting both.
I'm hearing anecdotally that many others have been experiencing this as well. I surprised that you don't have your own error reporting showing that this has been happening
|
|
Posts:
112
Registered:
6/22/06
|
|
|
|
Re: InsufficientInstanceCapacity: Insufficient capacity.
Posted:
Oct 6, 2009 7:52 AM PDT
in response to: flippyhead
|
|
|
Thank you for your response. However, you neglected to say which availability zone you targeted (US is a region). Does this mean you did not specify an availability zone (e.g. us-east-1a) in your launch request?
|
|
Posts:
4
Registered:
9/29/09
|
|
|
|
Re: InsufficientInstanceCapacity: Insufficient capacity.
Posted:
Oct 14, 2009 4:58 PM PDT
in response to: Udjeni
|
|
|
My apologies, yes this is all happening in EC2 us-east-1
I actually didn't originally reply to this because it seemed to have resolved itself, but now, it's happening again. I'm hearing anecdotal evidence from RightScale that other customers are experiencing this as well.
I have to say, this scares me. Our entire hosting model is predicated on being able to spin up instances as needed and we've again been unable to do so for the last 5 hours. I've made the attempt at least two dozen times.
|
|
Posts:
4
Registered:
9/29/09
|
|
|
|
Re: InsufficientInstanceCapacity: Insufficient capacity.
Posted:
Oct 15, 2009 9:17 AM PDT
in response to: flippyhead
|
|
|
Again this morning we've been able to successfully launch only ~50% of requested servers
Message was edited by: flippyhead
|
|
Posts:
10
Registered:
5/15/09
|
|
|
|
Re: InsufficientInstanceCapacity: Insufficient capacity.
Posted:
Oct 15, 2009 10:26 AM PDT
in response to: flippyhead
|
|
|
We've been having the same trouble all week. Zones us-east-1b, us-east-1c. We have a set of scripts that can launch instances; if we try repeatedly for several hours, sleeping every 15 seconds between launch requests, we can usually succeed in starting one.
We're using large and extra-large images; small images are out of the question for us.
-- david
|
|
Posts:
913
Registered:
12/13/06
|
|
|
|
Re: InsufficientInstanceCapacity: Insufficient capacity.
Posted:
Oct 16, 2009 11:33 AM PDT
in response to: flippyhead
|
|
|
We'd like to provide some additional information about what you can do should you receive an insufficient capacity response when submitting a request to launch new instances.
There can be short periods of time when we are unable to accommodate instance requests that are targeted to a specific Availability Zone. When a particular instance type experiences unexpected demand in an Availability Zone, our system must react by shifting capacity from one instance type to another. This can result in short periods of insufficient capacity. We incorporate this data into our capacity planning and try to manage all zones to have adequate capacity at all times. The following steps will ensure that you will have the best experience launching Amazon EC2 instances when an initial insufficient capacity message is received:
1. Don't specify an Availability Zone in your request unless necessary. By targeting a specific Availability Zone you eliminate our ability to satisfy that request by using our other available Availability Zones. Please note that a single RunInstances call will allocate all instances within a single Availability Zone.
2. If you require a large number of instances for a particular job, please request them in batches. The best practice to follow here is to request 25% of your total cluster size at a time. For example, if you want to launch 200 instances, launching 50 instances at a time will result in a better experience.
3. Try using a different instance type. As capacity varies across instance types, attempting to launch difference instance types provides spill over capacity should your primary instance type be temporarily unavailable.
Regards,
Justin
|
|
Posts:
10
Registered:
5/15/09
|
|
|
|
Re: InsufficientInstanceCapacity: Insufficient capacity.
Posted:
Oct 19, 2009 5:22 AM PDT
in response to: Justin@AWS
|
|
|
What about reserved instances? Will purchasing some of these solve the availability problem? Right now we're in a beta phase and we have a half-dozen participating customers. Their volumes are created in specific availability zones and we're not yet ready to do the work involved in making volumes zone-independent.
If we purchase six reserved instances, are we "guaranteed" that we'll be able to start our instances in a specified zone without encountering capacity problems?
Thanks.
-- david
|
|
Posts:
1,266
Registered:
10/10/07
|
|
|
|
Re: InsufficientInstanceCapacity: Insufficient capacity.
Posted:
Oct 19, 2009 6:15 AM PDT
in response to: saffrontech
|
|
|
Purchasing 6 reserved instances will guarantee that you will be able to start 6 [Linux] instances of the chosen type within the specified availability zone without running into any insufficient capacity errors.
|
|
|
|
Sign in to the AWS Management Console
Create an AWS Account
