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
Do we restart loops correctly in all kind of connection errors? E.g. RestartNeeded does it stop loop or restart? Or the only solution is to restart substrate-relay?
Possible improvement 1:
Now we are connected to the one exact node uri, e.g.:
yes we do caching, but, also I would like to check RPC/runtime calls (and subscribtions) monitoring to see what and how often we do RPC/runtime calls, if there is any space for optimization.
Also maybe, the separate 6-relayer setup could help by itself
Investigate/check
RestartNeeded
does it stop loop or restart? Or the only solution is to restart substrate-relay?Possible improvement 1:
Now we are connected to the one exact node uri, e.g.:
If the node is down, or has some problem, we could configure
list
ofuri
s, so whenRestartNeeded
, we rotate and try another uri, e.g.:So, if one node is overloaded, we just try another one.
Possible improvement 2 - connect substrate-relay to some "load balancer"
This "load balancer" would do routing to the live and not overloaded node, instead of handling this in our code.
Some logs from 2024-07-12/15
https://matrix.to/#/!FqmgUhjOliBGoncGwm:parity.io/$OjKXcX4aO9lkzM46fRLKXTMi-mf9vcpdJN_RDMgIn6o?via=parity.io
e.g.:
The text was updated successfully, but these errors were encountered: