-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
track: there could be a potential bug in transaction propagation. #1413
Comments
I probably have the same issue, as you have probably seen in the issue below yours. Can you please share your config with the "healthy" static nodes, that fixed it in your case? |
we're experiencing the same issue with v1.1.21, not sure about v1.1.18. I think it's related to #1397 |
@0xprincess , in version v1.1.19, this list of staticNodes is ok:
|
Have you tried to update your StaticNodes setting? |
Hey man, I work in the same company from @ayrat555. Do you mean trying to run 1.1.21 with the staticNodes from 1.1.19? |
I mean, try v1.1.21 with the config.toml in v1.1.21's mainnet.zip, the StaticNodes in config.toml was updated today. |
Yes, We are talking about this mainnet.zip version. The problematic version was this one. Here is de Node.P2P session of config.toml
|
just as a side note: I'm experiencing the same behaviour on the node-real fork of erigon, had a transaction in limbo for 14 hours yesterday. |
Just wanted to let you know that we're currently no longer experience this issue, we haven't update our static nodes so maybe they have upgraded or something. But it's still really strange behavior, when the ability to propagate your txs depends on the nodes you're connected to. And even if you connected to healthy nodes as well, the broken ones are still triggering this behavior. |
v1.2.x will no longer be supported, clean up these issue. |
System information
Geth version: v1.1.21
OS & Version: Linux
Commit hash : tag v1.1.21
Expected behavior
transactions could be propagated to other peers.
Actual behavior
transactions were not propagated to other peers, while block fetch is working.
Steps to reproduce the behavior
its configured
static nodes
may unhealthy any more, restart the client, send transaction to the client, you will see the txpool keeps growing and reach a very high level.It seems the received transactions were not propagated, so they are accumulating in the txpool, not consumed...
but after the client updated its static nodes to healthy ones, the problem disappear.
likely, there could be a potential bug, when connected to some
bad
node, in which case, the node can import block, but not able to propagate the transaction.Backtrace
No backtrace
The text was updated successfully, but these errors were encountered: