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

aws: make MaxRetries for API calls configurable #1787

Merged
merged 1 commit into from
May 4, 2015
Merged

aws: make MaxRetries for API calls configurable #1787

merged 1 commit into from
May 4, 2015

Conversation

koendc
Copy link

@koendc koendc commented May 3, 2015

  • Make it configurable in the AWS provider by add an option
    'max_retries'.
  • Set the default from 3 to 11 retries.

Fixes #1051

- Make it configurable in the AWS provider by add an option
  'max_retries'.
- Set the default from 3 to 11 retries.
@mitchellh
Copy link
Contributor

This LGTM. The upstream AWS provider also just merged some fixes for retries so I imagine that this will work even better. :)

@koendc
Copy link
Author

koendc commented May 4, 2015

Correct. At first, after we increased the max number of retries, we were hit by aws/aws-sdk-go#204:

Error: Post https://ec2.eu-west-1.amazonaws.com/: http: ContentLength=67 with Body length 0

After pulling last week's updates on aws-sdk-go with aws/aws-sdk-go#211 included, we got rid of retry/throttling-related errors.

@ghost
Copy link

ghost commented May 3, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators May 3, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add a way to handle the API rate limit on AWS
3 participants