Slow reindex probably due to high mempool

+1 vote
Hi,

My node has been reindexing for 3 weeks. Right now it has synchronized/checked 5kk out of 8kk blocks.

Mempool is very high, around 1.1k. My question is, what's the best way to handle this situation and what will happen if I restart multichain service during reindex process?

I'm not concerned about losing mempool since I can replicate the value(docs hash) of transactions. My primary goal is to get the node running correctly asap. Unfortunately, I do not have backup/snapshot of the node.

In advance, thank you for an assistance.
asked Sep 16 by venduim

1 Answer

+1 vote

There's a clearmempool command for this purpose:

https://www.multichain.com/developers/json-rpc-api/

answered Sep 17 by MultiChain
Thank you for your replay. Unfortunatelly, I'm unable to clear mempool with this command during reindex. It's getting instantly rebuilt (mempool is cleared just for a split second).
Is there any other way to clear mempool during reindex process or do you have any other idea what might cause the issue of slow reindexing?
Some feedback from the devs – before calling clearmempool, call:

pause incoming,mining,reaccepting

(The reaccepting parameter is unofficial.)

Then when the reindex is complete, call:

resume incoming,mining,reaccepting

Please let me know if that helps!
I was not able to clear mempool after only calling pause incoming,mining as per documentation. Sadly, I can't try it with reaccepting parameter since I've already deleted blocks/indexes db manually.
Right now I'm restoring the whole node 2mln blocks per 24h which is acceptable. To mitigate the issue of mempool I transfered new transaction from the backend of the application to burn address.

Fyi, I'm using Multichain version 2.3.3 and was not able to stop reindex process or clear mempool by restarting multichain/server.

Thank you for helping me with an issue!
...