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

fix(toolkit): CLI tool fails on CloudFormation Throttling #8711

Merged
merged 1 commit into from
Jun 24, 2020

Conversation

RomainMuller
Copy link
Contributor

@RomainMuller RomainMuller commented Jun 24, 2020

The CDK (particularly, cdk deploy) might crash after getting throttled
by CloudFormation, after the default configured 6 retries has been
reached.

This changes the retry configuration of the CloudFormation client (and
only that one) to allow up to 10 retries with a backoff base of 1
second. This makes the maximum back-off about 17 minutes, which I hope
would be plenty enough even for the 1 TPM calls. This should allow
heavily parallel deployments on the same account and region to avoid
getting killed by a throttle; but will reduce the responsiveness of the
progress UI.

Additionaly, configured a custom logger for the SDK, which would log the
SDK calls and other information

Fixes #5637


By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

@RomainMuller RomainMuller self-assigned this Jun 24, 2020
@mergify mergify bot added the contribution/core This is a PR that came from AWS. label Jun 24, 2020
The CDK (particularly, `cdk deploy`) might crash after getting throttled
by CloudFormation, after the default configured 6 retries has been
reached.

This changes the retry configuration of the CloudFormation client (and
only that one) to allow up to 10 retries with a backoff base of 1
second. This makes the maximum back-off about 17 minutes, which I hope
would be plenty enough even for the 1 TPM calls. This should allow
heavily parallel deployments on the same account and region to avoid
getting killed by a throttle; but will reduce the responsiveness of the
progress UI.

Additionaly, configured a custom logger for the SDK, which would log the
SDK calls to the console when running in debug mode, allowing the users
to gain visibility on more information for troubleshooting purposes.

Fixes #5637
@RomainMuller RomainMuller force-pushed the rmuller/retry-cloudformation-calls branch from daca70d to c94d386 Compare June 24, 2020 12:44
@RomainMuller RomainMuller added pr-linter/exempt-readme The PR linter will not require README changes pr-linter/exempt-test The PR linter will not require test changes labels Jun 24, 2020
@RomainMuller RomainMuller merged commit e512a40 into master Jun 24, 2020
@RomainMuller RomainMuller deleted the rmuller/retry-cloudformation-calls branch June 24, 2020 13:05
@aws-cdk-automation
Copy link
Collaborator

AWS CodeBuild CI Report

  • CodeBuild project: AutoBuildProject6AEA49D1-qxepHUsryhcu
  • Commit ID: daca70d
  • Result: SUCCEEDED
  • Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

@aws-cdk-automation
Copy link
Collaborator

AWS CodeBuild CI Report

  • CodeBuild project: AutoBuildProject6AEA49D1-qxepHUsryhcu
  • Commit ID: c94d386
  • Result: SUCCEEDED
  • Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
contribution/core This is a PR that came from AWS. pr-linter/exempt-readme The PR linter will not require README changes pr-linter/exempt-test The PR linter will not require test changes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Throttling: Rate exceeded
3 participants