-
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
v1.3.7 (pebbledb + PBSS): Peering issues - unable to connect or maintain peers #2145
Comments
Is it a new node just set up based on the bsc-snapshot? |
Let me investigate this. Meanwhile, here's what you can do:
What this does is that it will enable 1/2 connections to be dialed (the default is 1/3), and it might help to connect to more peers.
Thanks! |
@FerdyCai @kaladinlight do you guys mind sharing which region your nodes are running in? |
Node is bootstrapped from the bsc-snapshot. |
I will start with steps 1 and 2 and report back with debug if there is no improvement. Thanks for the suggestions! Also while talking about the |
I am running in us-east-2 (ohio) |
I am running in Singapore. |
|
You can also try the following method:
You can refer to in the README of snapshot of chapter Step 3: Replace Data |
Removed. And I don't know where the comment about deleting the |
Well, I thought the snapshot should have removed the "<datadir>/nodekey", so I removed the previous reply. But it turns out this PBSS+PebbleDB snapshot forget to remove the nodekey... So you do need to remove the nodekey this time, we will remove nodekey from snapshot in the future |
updated to #1947 |
Ha, well glad I caught it in my email. Thanks for the help sorting this issue! |
This really helps! Thanks. |
System information
Geth version:
v1.3.7
OS & Version: Linux
Expected behaviour
Establish and maintain a suitable pool of peer connections
Actual behaviour
Initial peering takes a significant amount of time resulting in the inability to sync on node start for up to 30 mins. Once a stable peer connection is established and the node finally starts syncing, there are never more than a handful (<5) peers ever connected. This results in any peers being dropped causing the node to stop syncing again and the inability to keep a node synced.
Steps to reproduce the behaviour
Backtrace
The text was updated successfully, but these errors were encountered: