Transaction that is added to a node's pool may not be propagated to the pools of its peer nodes

[nano-adhara]

Transaction that is added to a node's pool may not be propagated to the pools of its peer nodes

[nano-adhara]

I added the node execution arguments into the issue. This is using the sequenced node pool

[fab-10]

Hi @nano-adhara, I see where the issue is coming from, Besu has caches to remember txs exchanges with other peers, basically because we want to avoid to resend a tx multiple time to a peer (actually also the p2p protocol state that peers resending txs should be disconnected) and we also want to avoid reprocessing a tx that we have already seen.

Those caches are quite basic a the moment, so they could be improved to better handle scenarios like the one you are reporting, and I could take a look at them, trying to remove from these cache, valid txs that are dropped from the txpool, this needs to be done with care to avoid being exposed to attacks.

As last a question about your network, is it common for a valid tx to stay in the pool for so long that it could be evicted by the timer?

[nano-adhara]

Hello @fab-10,

So as an answer to your last question, is not happening that much, once a month, but the real problem with that is that whenever happens, the only solution is to restart the besu clients.

Ill include Fernando @chookly314 and Coenie @coeniebeyers in the topic to move forward in the conversation.