-
Notifications
You must be signed in to change notification settings - Fork 619
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
Understand current syncing time #3839
Comments
This issue has been automatically marked as stale because it has not had recent activity in the last 2 months. |
This issue has been automatically marked as stale because it has not had recent activity in the last 2 months. |
This issue has been automatically marked as stale because it has not had recent activity in the last 2 months. |
It is indeed unclear if it got stuck or if it just needs more time (it is trying to get through state sync for more than 1.5 hours already). It is a non-archival node running nearcore 1.29.0 release on mainnet. UPD: It took 4 hours to get through state sync, and after that the node is up and running just fine. |
Tracked around #8545. |
There have been multiple reports that the time it takes to sync a node to mainnet is quite suboptimal. It is important to understand where we are at with syncing in its current form and it may impact how we want to roll out the new syncing.
The text was updated successfully, but these errors were encountered: