You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@jclouds.apache.org by Nishant Chandra <ni...@gmail.com> on 2014/03/07 05:43:41 UTC
RequestLimitExceeded
Hi,
I am using v 1.7.1. When I try to start few Amazon EC2 nodes, I see the
following exception:
2014-03-07 03:09:27,063 [ERROR]
org.jclouds.aws.handlers.AWSServerErrorRetryHandler user thread 12 - Cannot
retry after server error, command has exceeded retry limit 5:
[method=public abstract java.util.Set
org.jclouds.aws.ec2.features.AWSInstanceApi.describeInstancesInRegion(java.lang.String,java.lang.String[])[us-west-1,
[Ljava.lang.String;@7e788896], request=POST
https://ec2.us-west-1.amazonaws.com/ HTTP/1.1]
2014-03-07 03:09:27,064 [ERROR] jclouds.compute user thread 12 - << problem
customizing node(us-west-1/i-c8236f97):
org.jclouds.aws.AWSResponseException: request POST
https://ec2.us-west-1.amazonaws.com/ HTTP/1.1 failed with code 503, error:
AWSError{requestId='4969dc9-71a2-457f-9b9f-c86b03b3a40',
requestToken='null', code='RequestLimitExceeded', message='Request limit
exceeded.', context='{Response=, Errors=}'}
at
org.jclouds.aws.handlers.ParseAWSErrorFromXmlContent.handleError(ParseAWSErrorFromXmlContent.java:77)
at
org.jclouds.http.handlers.DelegatingErrorHandler.handleError(DelegatingErrorHandler.java:69)
at
org.jclouds.http.internal.BaseHttpCommandExecutorService.shouldContinue(BaseHttpCommandExecutorService.java:180)
at
org.jclouds.http.internal.BaseHttpCommandExecutorService.invoke(BaseHttpCommandExecutorService.java:150)
at
org.jclouds.rest.internal.InvokeHttpMethod.invoke(InvokeHttpMethod.java:93)
at
org.jclouds.rest.internal.InvokeHttpMethod.apply(InvokeHttpMethod.java:76)
at
org.jclouds.rest.internal.InvokeHttpMethod.apply(InvokeHttpMethod.java:47)
at
org.jclouds.reflect.FunctionalReflection$FunctionalInvocationHandler.handleInvocation(FunctionalReflection.java:117)
at
com.google.common.reflect.AbstractInvocationHandler.invoke(AbstractInvocationHandler.java:79)
at com.sun.proxy.$Proxy56.describeInstancesInRegion(Unknown Source)
at
org.jclouds.ec2.compute.strategy.EC2GetNodeMetadataStrategy.getRunningInstanceInRegion(EC2GetNodeMetadataStrategy.java:68)
at
org.jclouds.aws.ec2.compute.strategy.AWSEC2GetNodeMetadataStrategy.getRunningInstanceInRegion(AWSEC2GetNodeMetadataStrategy.java:56)
What is the reason and probable fix for it?
--
Nishant
Re: RequestLimitExceeded
Posted by Jai M <ja...@gmail.com>.
Hi Nishant,
It means that you have reached the limit count for instances for
that region. Typically it is 20 instances per region. You need to
contact Amazon (there is a online request form) and increase your
instance limit or power down some of the running instances.
Rgds
Jai
On Thu, Mar 6, 2014 at 8:43 PM, Nishant Chandra
<ni...@gmail.com> wrote:
> Hi,
>
> I am using v 1.7.1. When I try to start few Amazon EC2 nodes, I see the
> following exception:
>
> 2014-03-07 03:09:27,063 [ERROR]
> org.jclouds.aws.handlers.AWSServerErrorRetryHandler user thread 12 - Cannot
> retry after server error, command has exceeded retry limit 5: [method=public
> abstract java.util.Set
> org.jclouds.aws.ec2.features.AWSInstanceApi.describeInstancesInRegion(java.lang.String,java.lang.String[])[us-west-1,
> [Ljava.lang.String;@7e788896], request=POST
> https://ec2.us-west-1.amazonaws.com/ HTTP/1.1]
> 2014-03-07 03:09:27,064 [ERROR] jclouds.compute user thread 12 - << problem
> customizing node(us-west-1/i-c8236f97):
> org.jclouds.aws.AWSResponseException: request POST
> https://ec2.us-west-1.amazonaws.com/ HTTP/1.1 failed with code 503, error:
> AWSError{requestId='4969dc9-71a2-457f-9b9f-c86b03b3a40',
> requestToken='null', code='RequestLimitExceeded', message='Request limit
> exceeded.', context='{Response=, Errors=}'}
> at
> org.jclouds.aws.handlers.ParseAWSErrorFromXmlContent.handleError(ParseAWSErrorFromXmlContent.java:77)
> at
> org.jclouds.http.handlers.DelegatingErrorHandler.handleError(DelegatingErrorHandler.java:69)
> at
> org.jclouds.http.internal.BaseHttpCommandExecutorService.shouldContinue(BaseHttpCommandExecutorService.java:180)
> at
> org.jclouds.http.internal.BaseHttpCommandExecutorService.invoke(BaseHttpCommandExecutorService.java:150)
> at
> org.jclouds.rest.internal.InvokeHttpMethod.invoke(InvokeHttpMethod.java:93)
> at
> org.jclouds.rest.internal.InvokeHttpMethod.apply(InvokeHttpMethod.java:76)
> at
> org.jclouds.rest.internal.InvokeHttpMethod.apply(InvokeHttpMethod.java:47)
> at
> org.jclouds.reflect.FunctionalReflection$FunctionalInvocationHandler.handleInvocation(FunctionalReflection.java:117)
> at
> com.google.common.reflect.AbstractInvocationHandler.invoke(AbstractInvocationHandler.java:79)
> at com.sun.proxy.$Proxy56.describeInstancesInRegion(Unknown Source)
> at
> org.jclouds.ec2.compute.strategy.EC2GetNodeMetadataStrategy.getRunningInstanceInRegion(EC2GetNodeMetadataStrategy.java:68)
> at
> org.jclouds.aws.ec2.compute.strategy.AWSEC2GetNodeMetadataStrategy.getRunningInstanceInRegion(AWSEC2GetNodeMetadataStrategy.java:56)
>
> What is the reason and probable fix for it?
>
> --
> Nishant