Skip to content
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

Closed
bowenwang1996 opened this issue Jan 21, 2021 · 5 comments
Closed

Understand current syncing time #3839

bowenwang1996 opened this issue Jan 21, 2021 · 5 comments
Assignees
Labels
A-chain Area: Chain, client & related T-core Team: issues relevant to the core team

Comments

@bowenwang1996
Copy link
Collaborator

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.

@bowenwang1996 bowenwang1996 added the A-chain Area: Chain, client & related label Jan 21, 2021
@bowenwang1996 bowenwang1996 added the T-core Team: issues relevant to the core team label Jun 29, 2021
@stale
Copy link

stale bot commented Sep 27, 2021

This issue has been automatically marked as stale because it has not had recent activity in the last 2 months.
It will be closed in 7 days if no further activity occurs.
Thank you for your contributions.

@stale stale bot added the S-stale label Sep 27, 2021
@stale
Copy link

stale bot commented Dec 27, 2021

This issue has been automatically marked as stale because it has not had recent activity in the last 2 months.
It will be closed in 7 days if no further activity occurs.
Thank you for your contributions.

@stale stale bot added the S-stale label Dec 27, 2021
@mzhangmzz mzhangmzz self-assigned this Jan 31, 2022
@stale
Copy link

stale bot commented May 2, 2022

This issue has been automatically marked as stale because it has not had recent activity in the last 2 months.
It will be closed in 7 days if no further activity occurs.
Thank you for your contributions.

@stale stale bot added the S-stale label May 2, 2022
@akhi3030 akhi3030 removed the S-stale label Jul 8, 2022
@frol
Copy link
Collaborator

frol commented Nov 8, 2022

image

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.

@Longarithm
Copy link
Member

Tracked around #8545.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-chain Area: Chain, client & related T-core Team: issues relevant to the core team
Projects
None yet
Development

No branches or pull requests

6 participants