-
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
Synchronization does not end for several days. #185
Comments
What're the IOPS of your storage device? Low/Mid-end SSDs won't cut it anymore. You really need NVMe to properly catch up. |
My knownStates value is around 300 million and I have been syncing in fast mode from scratch for 2 days. It would be great if someone could post a good knownStates number as of a certain date so we can get a sense for how close we are. A few things I did (I think) helped:
|
@attswk Yes, this problem has bothered me for many days, sometimes it stops syncing, or 1-5 block per 10s, we have been 3000+ blocks away. but now we have caught up the latest block.
This problem has been encountered by many people now, and I know that this does not get to the root of the problem, and can not be applied to everyone, but I hope it works for you. |
….13.5 Merge upstream v1.13.5
root@binance-core:~/go/src/github.com/binance-chain# curl -X POST -H 'Content-Type: application/json' -d '{"jsonrpc":"2.0","method":"eth_syncing","params":[],"id":1}' http://localhost:8545
{"jsonrpc":"2.0","id":1,"result":{"currentBlock":"0x6d661c","highestBlock":"0x6d6676","knownStates":"0x7c4d1e2","pulledStates":"0x7c4d1e1","startingBlock":"0x6c302e"}}
highestBlock - currentBlock = 40 ~ 130
The difference in height between 40 and 130 blocks is maintained and synchronization does not end.
The text was updated successfully, but these errors were encountered: