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.

Sign up for GitHub

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

Jump to bottom

Handle flaky or rate limited REST endpoints #29

Open
DavidNix opened this issue May 9, 2023 · 0 comments
Open

Handle flaky or rate limited REST endpoints #29

DavidNix opened this issue May 9, 2023 · 0 comments

Comments

@DavidNix
Copy link
Contributor

DavidNix commented May 9, 2023

I see the error with Notional but I'm able to curl it from my machine just fine.

time=2023-05-09T16:41:16.581-06:00 level=WARN msg="Job failed" job="Cosmos validator cosmosvalcons164q2kq3q3psj436t9p7swmdlh39rw73wpy6qx6: https://api-cosmoshub-ia.cosmosia.notional.ventures" error="Get \"https://api-cosmoshub-ia.cosmosia.notional.ventures/cosmos/slashing/v1beta1/signing_infos/cosmosvalcons164q2kq3q3psj436t9p7swmdlh39rw73wpy6qx6\": context deadline exceeded"

Also, there is a separate API call first that usually always succeeds. My guess is an aggressive rate limit (like 1 per sec).

Some options:

  • Retry mechanism
  • Rate limiting outgoing requests
  • Combination of both

However, we do not want the request to take too long (>10s). Otherwise, it risks causing back pressure on the WorkerPool.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@DavidNix