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
It is important to have the load value right as the node stability might be under the risk of not even being just overwhelmed by processing new requests, which is not far from the truth according to the queue length values, but rather causing the whole network to suffer from such speed degradation. The related issue is #544.
Update:
Below is an example of a deny to process a new request:
New content for 3be3416c805e4371 arrived 15Kb
RuntimeError: Queue is too long (4097 wallets), try again later
/usr/home/zold/.rvm/gems/ruby-2.5.3/gems/zold-0.17.5/lib/zold/node/async_entrance.rb:83:in `push'
The text was updated successfully, but these errors were encountered:
@denis-konovalyenko/z this project will fix the problem faster if you donate a few dollars to it; just click here and pay via Stripe, it's very fast, convenient and appreciated; thanks a lot!
The load average equals to
0
. For more details please refer to the http://91.211.13.180:4096/ response:And below is an example of actual values:

It is important to have the load value right as the node stability might be under the risk of not even being just overwhelmed by processing new requests, which is not far from the truth according to the queue length values, but rather causing the whole network to suffer from such speed degradation. The related issue is #544.
Update:
Below is an example of a deny to process a new request:
The text was updated successfully, but these errors were encountered: