Open utay opened 6 months ago
hi, thank you for the report. This looks like an issue we have seen elsewhere, we'll investigate and get back to you
This might be related to https://github.com/apollographql/router/pull/5235, which should land reasonably soon. If you wanted to try with that PR included, that might be a worthwhile try. 😄
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