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

Add retry logic to tx indexer calls #216

Open
jgryffindor opened this issue Jan 16, 2025 · 1 comment
Open

Add retry logic to tx indexer calls #216

jgryffindor opened this issue Jan 16, 2025 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@jgryffindor
Copy link
Contributor

jgryffindor commented Jan 16, 2025

Is your feature request related to a problem? Please describe.

Add retry logic to transaction history requests to the indexer to catch cases where the indexer is malfunctioning or local scheme caches are different on secondary nodes.

Describe the solution you'd like

Add the fix you described to retry on failures 503 with backoff

userQuery for indexer calls

Describe alternatives you've considered

Cloudflare origin pools - not ideal to create a backend pool for each endpoint to handle failures

@jgryffindor jgryffindor added the enhancement New feature or request label Jan 16, 2025
@jgryffindor jgryffindor changed the title Feature - add retry logic to tx indexer calls Add retry logic to tx indexer calls Jan 16, 2025
@fmorency fmorency assigned hansl and unassigned chalabi2 Jan 31, 2025
@hansl
Copy link
Contributor

hansl commented Feb 13, 2025

I don't know how to test this, @jgryffindor. If you could help me test it, that'd be great. Right now if I just drop 99% of requests (in Chrome's network devtools) it will retry automatically. It might not respond the same with status 503.

Please advise.

@hansl hansl assigned jgryffindor and unassigned hansl Feb 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants