-
Notifications
You must be signed in to change notification settings - Fork 131
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
Rate Exceeded Error #95
Comments
@DanDubinsky can you give more details? Like When it started happening exactly and do you see any errors logged in the agent? |
First error was May 7, 2018 around 4PM Eastern Time. We've been getting the error about every other build since then. The error in the Jenkins console was: Rate exceeded (Service: AmazonCodeDeploy; Status Code: 400; Error Code: ThrottlingException; Request ID: d494fea1-52c1-11e8-9335-bdce7ca12b64) |
Hi, We have been working on improving efficiency of our internal calls. Is this still affecting you? If so, can you please add information about how your Jenkins box is set up? Thank you |
We've been using the Code Deploy Jenkins plug in for about a year with no trouble. Then about 2 weeks ago we started getting errors like this about every other build:
Failed CodeDeploy post-build step; exception follows.
Rate exceeded (Service: AmazonCodeDeploy; Status Code: 400; Error Code: ThrottlingException;
The deploys actually succeeds, but Jenkins reports it as a failure. Amazon support says the problem is with the GetDeployment API, the polling that the plug in does to see if the deployment is successful. They say our Jenkins server is sending 41 of those per minute with higher bursts. They say the bursts are causing the error. We have the polling interval set to 5 seconds.
Anybody have any ideas? Seems to me the problem must be on the Amazon side since we haven't changed anything on the Jenkins server in months. Amazon is insisting that the problem is with Jenkins.
The text was updated successfully, but these errors were encountered: