You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Pull based transaction pool sync: Current rebroadcast logic is not robust; nodes that initiate transactions are the ones rebroadcasting. But due to the delay in propagating the transactions can still arrive out of order and therefore be rejected. Also, if a node restarts outside the rebroadcast window which is 50mins, then they don't receive any of the old transactions since mempool is not persisted across restarts. Mempool can be persisted but there is still the issue of transactions dropping when received out of order.
To get around this, one solution is for nodes to request transactions from peers after catchup and/or periodically when synced.
Adding bitswap should alleviate the issue further as transactions can be forwarded with minimum delay
Preliminary Checks
Description
During high traffic such as staking payouts, nodes drop transactions requiring senders to retry multiple times
Steps to Reproduce
Create simple value transfer txns once in 3-5 seconds in total # of txn to be ~150-200
Expected Result
Transactions should be included in blocks
Actual Result
Some transactions get dropped
Daemon version
How frequently do you see this issue?
Frequently
What is the impact of this issue on your ability to run a node?
High
Status
Additional information
Related tickets
Transactions removed from mempool
Investigate: Inconsistent Transaction Pool Sizes on gossipqa
payment transaction dropped after inclusion in orphan
Issues with the mempool empty. My mempool is different from the others.
#9868
Potential solutions:
To get around this, one solution is for nodes to request transactions from peers after catchup and/or periodically when synced.
The text was updated successfully, but these errors were encountered: