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

Is it possible to set a request timeout on the server? #251

Closed
jaffemd opened this issue Dec 2, 2024 · 2 comments · Fixed by #254
Closed

Is it possible to set a request timeout on the server? #251

jaffemd opened this issue Dec 2, 2024 · 2 comments · Fixed by #254

Comments

@jaffemd
Copy link

jaffemd commented Dec 2, 2024

We have the hive gateway set up in the supergraph configuration reading from a static supergraph.graphql file. It does not appear like there's an option currently to do this, looking through the gateway server code, it looks like the requestTimeout option would need to be passed in here.

Our current workaround is to set the timeout on the graphql datasources directly on the supergraph schema. However, ideally we'd like to be able to set an overall request timeout on the server itself rather than relying on the fetch resolution timeouts to subgraphs.

@ardatan
Copy link
Member

ardatan commented Dec 3, 2024

Thanks for the feature request!
#254
Is this what you needed?

@jaffemd
Copy link
Author

jaffemd commented Dec 3, 2024

Yes, that would be great, thank you! In the mean time, we were able to figure out how to use transportEntries to configure a timeout for each subgraph at runtime. If there was some additional documentation on that option, I think it would have saved us some time.

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

Successfully merging a pull request may close this issue.

2 participants