-
Notifications
You must be signed in to change notification settings - Fork 272
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
Request retries for subgraph queries #2006
Conversation
This comment has been minimized.
This comment has been minimized.
retries require a clonable request so it is now implemented on subgraph::Request
I added some configuration options, marked as experimental, so we can move forward on this and at least have some form of retries, before we settle on the policy configuration format. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we open a followup issue on documentation? I think I have an intuition on how to customize it, but it s all still fuzzy to me
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approved, but I do think documentation should be added as part of this PR.
did we decide where documentation should be written for experimental features? |
@Geal On my side for logging and tracing I wrote the documentation in the related section. For tracing in tracing.mdx for example. And just mark it as experimental |
alright, there's docs now. I feel like the traffic shaping doc could benefit from longer explanations of each feature, and maybe a description of their order and interaction |
also, as a follow-up, I think I'll add an option on retries, to deactivate them on mutations if necessary (not all mutations are idempotent) |
implements retries for subgraph requests. This uses Finagle's retry buckets algorithm
Fix: #338
Fix: #1956