-
-
Notifications
You must be signed in to change notification settings - Fork 33
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
timeout reached while waiting for fetchSockets response #234
Comments
These two issues are related: |
The error is from Possible solutions are increase the adapter timeout or scale/tune the redis. Raising the timeout seems pointless as it is not fixing the root problem (redis perf). And since we are curenlty focusing on stabilizing without infra updates, I am closing the issue. |
90% of the time issue happens because of many parallel probes connecting to the API simultaneously on the API start/restart. jsdelivr/globalping-probe#179 will help here partially, other part of fix is perf tuning. When #418 is finished, we will have an environment to test different approaches like #419 or #307 |
The text was updated successfully, but these errors were encountered: