user86833: I just started my 'occasional' full-node and I am watching the size of the mempool grow after full block synchronization - watch -n 3 'bitcoin-cli getrawmempool true |jq "length"' - it has around 4000 pending transactions. My 'continuous' full-node, however, has around 18000 pending transactions which seem to never become available to my 'ocasional' node. 
Looks like that when a node starts up it will receive the new transactions that arrive at the mempool, but the old transactions that had been laying there are never 'synchronized'. How can I synchronize the mempool of a recently launched node with the one of its peers?
I could shut down my other full-node and copy past mempool.dat into my other node but this solution is very ugly as I need to shut down a long-running node with many connections.

user61002: mempoolcp command line utility is what you are looking for:
https://github.com/dev7ba/mempoolcp

86833: <p>I just started my 'occasional' full-node and I am watching the size of the mempool grow after full block synchronization - <code>watch -n 3 'bitcoin-cli getrawmempool true |jq "length"'</code> - it has around 4000 pending transactions. My 'continuous' full-node, however, has around 18000 pending transactions which seem to never become available to my 'ocasional' node. </p>

<p>Looks like that when a node starts up it will receive the new transactions that arrive at the mempool, but the old transactions that had been laying there are never 'synchronized'. How can I synchronize the mempool of a recently launched node with the one of its peers?</p>

<p>I could shut down my other full-node and copy past <code>mempool.dat</code> into my other node but this solution is very ugly as I need to shut down a long-running node with many connections.</p>
 61002: <p>mempoolcp command line utility is what you are looking for:</p>
<p><a href="https://github.com/dev7ba/mempoolcp" rel="nofollow noreferrer">https://github.com/dev7ba/mempoolcp</a></p>
