nodejs-pool
nodejs-pool copied to clipboard
Snipa22
How to fix long runner?
My modules are still using multiple gbs or memory for some reason
https://imgur.com/a/0Lovemg
Does anyone know how I can fix this?
It's eating memory but you provide us with no other information. :( What coin? pm2 logs longRunner What height does longRunner show scanning from? Is it showing within the last 30 blocks on the network? If so, you're fine. longRunner is constantly running to ensure LMDB doesn't get too full of old stuff.
In my experience, longRunner would eat tons of memory and cpu if it were doing it's job constantly prior to a patch where longRunner would get stuck on an invalid block. This also caused LMDB to grow massively quick and caused all sorts of mayhem.
Also, don't be alarmed when it takes up that much memory. Here's my pm2 monit from a 40Mh+ AEON pool overthrown with ASICs: https://imgur.com/a/8QmJBkW
It's going to be okay. :D :D
It is for Aeon pool and it only 10 blocks behind I think. it was not always like this only recently when I changed to a new wallet with rebase :(
We have found blocks and all payments are going out, but this will probably become a problem soon as we are only a small pool really they were in the 100s of mbs not gbs :(
@camthegeek Nice to hear your idea. Can you pull request the longRunner patch on this Snipa’s repo or MO’s repo ? The bug still exists ( I runned into it recently, database keeps growing even with server restarts blah blah ).
