Closed tianwangchn closed 3 years ago
This is an indication that your node is not keeping up with all the incoming transactions into it.
This is an indication that your node is not keeping up with all the incoming transactions into it.
Hi heifner, Thanks for your response. Is that a hardware defect? My server's CPU is 8c16t up to 4.2GHz.
Do you know how many peers are connected to you? Are you servicing a lot of http requests? What version of eosio are you running? Are you running on a SSD? How much physical RAM do you have?
Do you know how many peers are connected to you? Are you servicing a lot of http requests? What version of eosio are you running? Are you running on a SSD? How much physical RAM do you have?
Hi heifner, Thank u very much. There is no peer connected to me; Yes, I'm servicing a lot of http requests for stress testing, it is about 1000 requests per second; The version of eosio is v2.0.5-de78b49b5765c88f4e005046d1489c3905985b94; Yes, I use a M.2 SSD; The RAM size is 8GB.
What's more, I set "net-threads = 8" and it works well now.
Set "net-threads = 8" does not solve this issue. Reducing http requests to 200 times per second seems works.
Hi guys, I met a problem when I was running Nodeos. At the beginning, everything is ok and the blocks syn is fine. But, after about 3 hours I found I can't get block info from my node, so I went to check the Nodeos, I found this info and every info is all the same.
Dropping trx a84e9b759851540b65d75fd770040c48a7ae7547efd32c1a242b1ab49d98bb60, too many trx in progress 104878912 bytes
And my config.ini is like this,
Please help me, thanks a lot!