-
Notifications
You must be signed in to change notification settings - Fork 416
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
Version 1.2.12 slow syncing #3263
Comments
Has your import process on 1.2.12 finished yet? How long did it take in total? The |
It's only up to 2245276 right now. |
So your node is on the current blockchain height |
No it's still way behind. For example I'm only on block 2248073 now and current on wavesexplorer is 2249822 so still over 24 hours behind even after running 11 days. |
Compare block headers /blocks/headers/at/2248073 of your node and official node, please. The And could you send me log file |
It's on the right chain, it's just syncing extremely slowly. Normally I keep the log off, I turned it on now and will post one later on. |
How is it going? |
Not well, I've also tried it on a dedicated server with a lot more power as well and it's a bit faster but still crawling. I don't see any errors in the log or anything. Right now I'm just watching http://blockchain.wavesnodes.com/ daily and hope if I can load the next blockchain snapshot fast enough it might be able to catch up. |
It has caught up now. 25 days to sync is pretty crazy :( |
So did you turn logs on? Could you send it? |
Closed due to inactivity. Please feel free to reopen the issue if this problem is still actual. |
It is definitely still slow, I updated to the latest about 24 hours ago since I was having rollback issues and saw there was an update. It was only 2000 blocks behind at that time and now it is 700 blocks behind still. |
Def still an issue in version 1.3.6. I had to move Waves to a new server and downloaded the latest snapshot and it's as slow as ever syncing up from there :( See the timestamps from the log:
|
hi, @Crypto2 |
Describe the bug
We just updated to 1.2.12 yesterday from 1.1.11 and installed the new blockchain as per directions from https://docs.waves.tech/en/waves-node/options-for-getting-actual-blockchain/state-downloading-and-applying
Since then syncing has been crawling, taking an hour to do 100-200 blocks. It is the only thing running on the system other than just the core Linux system (Debian 10.5 64-bit) and only about 50% of RAM is in use and practically no swap in use.
No sure what is going on. Maybe are there any changes to waves.conf from 1.1.x to 1.2.x that need to be made? Not seeing any errors on the log except the occasional:
2020-09-09 20:02:23,050 WARN [ecution-context-global-32] kamon.metric.Timer - Failed to record value [18984192277738] on [span.processing-time,{operation=block-appender,error=true}] because the value is outside of the configured range. The recorded value was adjusted to the highest trackable value [3600000000000]. You might need to change your dynamic range configuration for this metric
Expected behavior
Syncing at a much faster speed.
The text was updated successfully, but these errors were encountered: