Update maxmempool at runtime #10435

issue shivaenigma opened this issue on May 20, 2017

shivaenigma commented at 6:39 AM on May 20, 2017: none

It would be good to increase/decrease maxmempool without restarting bitcoind. The issue right now is that after restarting the node, it again takes half a day to catch up with all the currrent unconfirmed transactions. There seems to be no way to restart and quickly getting back the unconfirmed tx list.

Many times the webmaster wants to tweak maxmempool to handle memory issues.
fanquake added the label Mempool on May 20, 2017
paveljanik commented at 6:46 AM on May 20, 2017: contributor

Eh? We are dumping mempool at shutdown and loading it again at the start...
jnewbery commented at 6:57 PM on May 22, 2017: member

@shivaenigma what version of bitcoind are you running? Since v0.14.0, mempool is stored to disk on shutdown and reloaded on startup. If you're stop-starting the bitcoind client you don't need to wait half a day to catch up with unconfirmed transactions.

This was added in #8448
shivaenigma commented at 5:04 AM on May 23, 2017: none

@jnewbery I am on 0.13 . This is exactly what I needed. Thanks a lot Closing in favour of #8448
shivaenigma closed this on May 23, 2017
MarcoFalke locked this on Sep 8, 2021

Contributors

Labels