-
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 around 3 minutes behind head for two days #149
Comments
Thanks! But after a few hours, I get a previous error again:
Too many problems. I'll just look for alternative clients. Thanks. |
I have the same issue( as per the initial post in this thread), and node not sync'd now |
Some time ago was possible to sync with these specs, but right now, BSC has many txs, so it is not possible. You need to upgrade your hardware. |
what hardware can you suggest as minimum? |
I'm about to order the following:
My estimation is an expense of around $500. But that's just a try, not based on any metric. I have no enough information. |
Our specs meet the minimum stated requirements for hardware and we restarted the node with --cache , but still it takes a while to sync up.... Is there any information I can provide, that might help diagnose the problem better ? currently I see WARN messages in the logs, WARN [04-21|04:59:43.934] Pivot became stale, moving old=6750213 new=6750278
and the state of sync, has been 100 blocks or so, behind for almost a week now. The size on disk is 102GB, and it seems to sync, about 1 or 2 GB ( if that ) per day. |
Seeing this issue as well. |
@AlexWD please download the latest |
which is the latest 'config.toml' ? is it not 1.0.7 ? |
Tried with newest config still the issue occurs. |
Please do use native NVMe SSD insteads of SATA SSD(or EBS on AWS), or it will never complete the sync. |
…ngine-api-size Increase the maximum size for engine API requests via http
After some problems I decided going with a new fast sync from scratch.
For two days the block's age was continuously reduced until reaching a value of around 3 minutes. But after two more days this value is stuck at around same value.
My hardware is a Raspberry Pi 4 (8 GB) with an USB3 SSD (write speed > 300 MB/s). CPU load remains below 1 and there's no heavy IO activity.
This is an extract of the log (filtered to show only Pivot became stale, moving and lines with age information):
My only concern is if this will eventually get synced or if this will be forever behind the head.
I think there's a lack of metrics tools or diagnostics information to get an idea of the ETA, global status and even the viability of the process.
The text was updated successfully, but these errors were encountered: