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

Handle rate limiting gracefully #184

Closed
solarnz opened this issue Feb 27, 2020 · 6 comments
Closed

Handle rate limiting gracefully #184

solarnz opened this issue Feb 27, 2020 · 6 comments

Comments

@solarnz
Copy link

solarnz commented Feb 27, 2020

Terraform Version

Terraform v0.12.21
+ provider.pagerduty v1.4.2

Affected Resource(s)

  • pagerduty_schedule

However, this might apply to the other pagerduty resources as well

Debug Output

Panic Output

Expected Behavior

The plan / apply of terraform should have respected the ratelimit and slowed down.

Actual Behavior

Error: Error reading: PA6AZJI: GET API call to https://api.pagerduty.com/schedules/PA6AZJI failed: 429 Too Many Requests
Error: Error reading: PJU8HLA: GET API call to https://api.pagerduty.com/schedules/PJU8HLA failed: 429 Too Many Requests
Error: Error reading: PI9OEWZ: GET API call to https://api.pagerduty.com/schedules/PI9OEWZ failed: 429 Too Many Requests
Error: Error reading: PV6IYLZ: GET API call to https://api.pagerduty.com/schedules/PV6IYLZ failed: 429 Too Many Requests
Error: Error reading: PG8PQG5: GET API call to https://api.pagerduty.com/schedules/PG8PQG5 failed: 429 Too Many Requests
Error: Error reading: PCWYMEQ: GET API call to https://api.pagerduty.com/schedules/PCWYMEQ failed: 429 Too Many Requests
Error: Error reading: PLNGGH3: GET API call to https://api.pagerduty.com/schedules/PLNGGH3 failed: 429 Too Many Requests
Error: Error reading: PRSIB5G: GET API call to https://api.pagerduty.com/schedules/PRSIB5G failed: 429 Too Many Requests

Steps to Reproduce

  1. terraform plan or terraform apply with many pagerduty resources such as users, schedules, services and escalation policies.

Important Factoids

Currently, locally I have

40x pagerduty_escalation_policy
34x pagerduty_extension
67x pagerduty_schedule
67x pagerduty_service
52x pagerduty_user

References

@apnordcloud
Copy link

I'm experiencing same problem.

Terraform Version

Terraform v0.12.21
+ provider.pagerduty v1.5.0

Affected Resource

pagerduty_service_integration

Actual Behavior

Error: Error reading: XXXXXXX: Get https://api.pagerduty.com/services/XXXXXXX: read tcp 10.1.0.4:57122->44.227.224.80:443: read: connection reset by peer

Error: Error reading: XXXXXXX: Get https://api.pagerduty.com/services/XXXXXXX: http2: server sent GOAWAY and closed the connection; LastStreamID=1399, ErrCode=NO_ERROR, debug=""

@h3x89
Copy link

h3x89 commented Mar 21, 2020

@stmcallister
Copy link
Contributor

Hello! #198 added a catch and retry on 429s. Please let me know if you're still experiencing this issue.

@stmcallister
Copy link
Contributor

Going to close this issue. Please create another issue if you have further troubles.

@solarnz
Copy link
Author

solarnz commented May 15, 2020

Sorry for taking a while to respond, but I'm still encountering the same issue

Error: GET API call to https://api.pagerduty.com/schedules/PG8PQG5 failed: 429 Too Many Requests
Error: GET API call to https://api.pagerduty.com/schedules/PR86CI2 failed: 429 Too Many Requests
Error: GET API call to https://api.pagerduty.com/schedules/P1T284U failed: 429 Too Many Requests
Error: GET API call to https://api.pagerduty.com/schedules/PPBUZML failed: 429 Too Many Requests
Error: GET API call to https://api.pagerduty.com/schedules/PUHUDXS failed: 429 Too Many Requests
Error: GET API call to https://api.pagerduty.com/schedules/PFA6LCV failed: 429 Too Many Requests

@bennettp123
Copy link

Hello! #198 added a catch and retry on 429s. Please let me know if you're still experiencing this issue.

I think this was added in #191

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

5 participants