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
Hey guys,
After talking to some of the node runners,
I have aggregated a couple of the common issues (Thanks ddn)
A) mech requests do not expire. Therefore if for some reason the mech does not respond to a request (For example if the system is overloaded) the trader is then stuck waiting for a response. This means that there are not any more transactions leading to a failure to meet KPIs
B) Very very occasional 413 request issue.
- This is caused by a rpc request being too large Interestingly, this only appears to affect quicknode operators with no reports from nodies.app experiencing this issue
- we have not isolated exactly what the request is.
- Symptoms are looping of the agent where it will keep retrying the failing request generating the 413 issue.
- this looping also causes the agent to miss its performance metrics without a restart.
The text was updated successfully, but these errors were encountered:
Hey guys,
After talking to some of the node runners,
I have aggregated a couple of the common issues (Thanks ddn)
A) mech requests do not expire. Therefore if for some reason the mech does not respond to a request (For example if the system is overloaded) the trader is then stuck waiting for a response. This means that there are not any more transactions leading to a failure to meet KPIs
B) Very very occasional 413 request issue.
- This is caused by a rpc request being
too large
Interestingly, this only appears to affect quicknode operators with no reports from nodies.app experiencing this issue- we have not isolated exactly what the request is.
- Symptoms are looping of the agent where it will keep retrying the failing request generating the 413 issue.
- this looping also causes the agent to miss its performance metrics without a restart.
The text was updated successfully, but these errors were encountered: