-
Notifications
You must be signed in to change notification settings - Fork 897
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
Slow backwards sync #4446
Comments
I also get the error NO_PEERS_FOUND sometimes
|
I agree we can improve the logging, showing only the progress and critical errors, and pushing transient errors to debug. Instead for the timing, it is normal that it takes more time that the initial sync, since backward sync needs to fully import blocks, in a serial way, so the improvements around block import that are ongoing will benefit backward sync as well, but as rule of thumb, if Besu is down for some day is usually faster to delete the database and perform a snapsync from scratch, that wait for the backward sync to complete, since the latter is only meant for the sync of few blocks. |
Understood - maybe we paste that in the logs if the BWS queue is large enough? Or a docs change - I will open a PR on this page. |
Description
Had Besu shutoff for a week due to some issues, now restarted with 2.7.4, and it is slowly doing Backwards Sync Algorithm, it has been 15 hours, and seems like it will be another 24 hours at this rate. CPU is low at 10%, and load is 1.4, io is low. I am running as part of rocketpool tool. 16GB Ram, '--Xplugin-rocksdb-high-spec-enabled'
I do have grafana dashboard running, so can include any plots for that if wanted.
The text was updated successfully, but these errors were encountered: