Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Throttle requests to EC2 API #170

Closed
bignastybryce opened this issue Jul 1, 2015 · 2 comments
Closed

Throttle requests to EC2 API #170

bignastybryce opened this issue Jul 1, 2015 · 2 comments

Comments

@bignastybryce
Copy link

When running kitchen converge or test with --concurrency greater than 10, one or more of the VMs will usually not be created. When I try the same concurrency with kitchen create, I get this exception:

>>>>>> ------Exception-------
>>>>>> Class: Kitchen::ActionFailed
>>>>>> Message: Failed to complete #create action: [Request limit exceeded.]
>>>>>> ----------------------
>>>>>> Please see .kitchen/logs/kitchen.log for more details
>>>>>> Also try running `kitchen diagnose --all` for configuration

I have a workaround which I think also proves the problem: In my Thorfile I have separated the destroy/create/converge/verify/destroy steps into separate commands, and run the create and destroy steps with --concurrency=10, with the rest at full concurrency.

I'm running 15 suites concurrently, with one of the instances having an extra EBS volume.

I don't know if this issue belongs here, or in the test-kitchen project itself.

Thanks,
-Bryce.

@bignastybryce
Copy link
Author

I should mention that I have set my retryable_sleep config to 30 seconds, instead of the default 5, which doesn't affect this error.

@tyler-ball
Copy link
Contributor

This is a duplicate of #44 so I'm going to close this, but I'll port your comments over there

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants