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
In production a router process serves hundreds of requests per second; when it hot reloads because the supergraph has been refreshed, a few requests get 502s from the load balancer because it got connection refused on the router.
To Reproduce
I've been able to reproduce pretty consistently:
Start the router with hot reload enabled
Run any load testing tool such as ab -n 1000000 -c 20 http://127.0.0.1:4000/graphql
Modify the supergraph to make the router reload
💥 Right around "reload complete", at least one request will fail with connection refused
Expected behavior
I'd expect 0 downtime as per the docs.
Additional context
Router 1.45.0
The text was updated successfully, but these errors were encountered:
Describe the bug
In production a router process serves hundreds of requests per second; when it hot reloads because the supergraph has been refreshed, a few requests get 502s from the load balancer because it got connection refused on the router.
To Reproduce
I've been able to reproduce pretty consistently:
ab -n 1000000 -c 20 http://127.0.0.1:4000/graphql
Expected behavior
I'd expect 0 downtime as per the docs.
Additional context
The text was updated successfully, but these errors were encountered: