-
Notifications
You must be signed in to change notification settings - Fork 1.7k
No Snapshots downloaded when using warp with Ubuntu 16 #6297
Comments
Note, |
Snapshot sync only kicks in if the node is more than 100000 blocks behind the head of the chain. We might want to revise that constant given that recent blocks are much slower to process. |
I'm running into the exact same issue here. Then it starts syncing one block at a time, which will take me ages to catch up to the latest block. |
@PhABC yes, this is due to the huge amount of transactions per day currently processed by the Ethereum blockchain. 100k blocks used to be no issue one year ago. |
Any way to force snapshotting? Version 1.7.10 and 1.8.4beta is not fetching snapshots at all, sync is horribly slow. It used to fetch snapshots though, it's weird, but no more. |
Try to remove your nodes.json and increase the number of --snapshot-peers |
This should not have been closed: confirmed behavior in 1.8.4: no snapshots are used either before or after deleting the db. |
Using the
parity --warp
command in my Ubuntu 16 console, I was expecting to see some snapshots being downloaded via the warp function. Not specifying the--warp
argument results in the same behavior, where no snapshots seem to be downloaded. My girlfriend synced her parity on her windows machine in about 15 minutes after not opening it for > 1 months, and it took me about the same time to sync the few hours I missed while my linux machine wasn't syncing. I could see in her log that snapshots were downloaded, but I personally only see that parity is "syncing" (see this image).The text was updated successfully, but these errors were encountered: