You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Can you please add a documentation on using AbortController on SSR (Server side rendering)?
We came across a problem recently where a lot of requests that our React SSR Apollo client(hosted in Node) is sending to Apollo server(hosted in Node) are not timing out for very long time.
We have native timeouts on both SSR and Apollo server node processes ex. https://nodejs.org/api/http.html#serversettimeoutmsecs-callback.
However, even with Apollo server timing out client request(client is SSR in this case), a lot of GraphQL queries are still left as "orphaned" and are stuck for 200-300 seconds 😏
We are implementing a cancellation mechanism using AbortController, but didn't find any proper documentation around using it. Of course we went through the issue history, checking out source code, as well as other implementations:
Hey team,
Can you please add a documentation on using AbortController on SSR (Server side rendering)?
We came across a problem recently where a lot of requests that our React SSR Apollo client(hosted in Node) is sending to Apollo server(hosted in Node) are not timing out for very long time.
We have native timeouts on both SSR and Apollo server node processes ex. https://nodejs.org/api/http.html#serversettimeoutmsecs-callback.
However, even with Apollo server timing out client request(client is SSR in this case), a lot of GraphQL queries are still left as "orphaned" and are stuck for 200-300 seconds 😏
We are implementing a cancellation mechanism using AbortController, but didn't find any proper documentation around using it. Of course we went through the issue history, checking out source code, as well as other implementations:
It will be helpful if there's an official guide on using AbortController in SSR (or just client side).
Kudos!
The text was updated successfully, but these errors were encountered: