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
endpoint2 is intentionally taken down and only endpoint1 is working, however,
when sending queries on the gateway, I am occassionally receiving errors about ECONNREFUSED on endpoint2.
The load balancing mechanism should first do a test ping if the host is reachable before sending a request.
The text was updated successfully, but these errors were encountered:
I think there is a bug in undici BalancedPool that routes requests to an upstream even if it could not connect there, and it does not retry/send it elsewhere in case it fails to connect. Things stabilizes over time because of BalancedPool algorithm, so only a few number of requests would fail.
The bad news is that I don't have time right now to fix it there.
I think there is a bug in undici BalancedPool that routes requests to an upstream even if it could not connect there, and it does not retry/send it elsewhere in case it fails to connect. Things stabilizes over time because of BalancedPool algorithm, so only a few number of requests would fail.
The bad news is that I don't have time right now to fix it there.
Yes! I noticed that the balancing algorithm eventually only selects the online server after sending some requests.
Title says
I am encountering a scenario where I provide 2 URLs for a single subgraph in an array form
endpoint2 is intentionally taken down and only endpoint1 is working, however,
when sending queries on the gateway, I am occassionally receiving errors about ECONNREFUSED on endpoint2.
The load balancing mechanism should first do a test ping if the host is reachable before sending a request.
The text was updated successfully, but these errors were encountered: