Skip to content
This repository has been archived by the owner on Nov 6, 2020. It is now read-only.

No Snapshots downloaded when using warp with Ubuntu 16 #6297

Closed
PhABC opened this issue Aug 14, 2017 · 9 comments
Closed

No Snapshots downloaded when using warp with Ubuntu 16 #6297

PhABC opened this issue Aug 14, 2017 · 9 comments
Labels
F3-annoyance 💩 The client behaves within expectations, however this “expected behaviour” itself is at issue. M4-core ⛓ Core client code / Rust.
Milestone

Comments

@PhABC
Copy link

PhABC commented Aug 14, 2017

I'm running:

  • Parity version: 1.7.0
  • Operating system: Linux
  • And installed: via binaries

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).


@PhABC PhABC changed the title No Snapshots download when using warp with Ubuntu 16 No Snapshots downloaded when using warp with Ubuntu 16 Aug 14, 2017
@5chdn 5chdn added the Z1-question 🙋‍♀️ Issue is a question. Closer should answer. label Aug 15, 2017
@5chdn
Copy link
Contributor

5chdn commented Aug 15, 2017

Note, --warp is enabled by default and the flag does nothing. If you have issues with snapshot restoration, try adding additional warp sync peers with something like --snapshot-peers 15.

@arkpar
Copy link
Collaborator

arkpar commented Aug 15, 2017

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.

@PhABC
Copy link
Author

PhABC commented Aug 15, 2017

@5chdn Yes I know, just wanted to make it explicit. I will try to use the `snapshot-peers' argument next time.

@arkpar 100k seems like a lot. Even 10k can take up to 1-2 hours.

@kommen
Copy link

kommen commented Aug 16, 2017

I'm running into the exact same issue here.
Partity 1.7.0 on Ubuntu 16.

Then it starts syncing one block at a time, which will take me ages to catch up to the latest block.

@5chdn
Copy link
Contributor

5chdn commented Aug 16, 2017

@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.

@5chdn 5chdn added F3-annoyance 💩 The client behaves within expectations, however this “expected behaviour” itself is at issue. M4-core ⛓ Core client code / Rust. and removed Z1-question 🙋‍♀️ Issue is a question. Closer should answer. labels Aug 16, 2017
@5chdn 5chdn closed this as completed Aug 22, 2017
@eldoy
Copy link

eldoy commented Dec 22, 2017

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.

@5chdn 5chdn added this to the 1.9 milestone Jan 2, 2018
@5chdn
Copy link
Contributor

5chdn commented Jan 2, 2018

Try to remove your nodes.json and increase the number of --snapshot-peers

@slavicd
Copy link

slavicd commented Jan 4, 2018

This should not have been closed: confirmed behavior in 1.8.4: no snapshots are used either before or after deleting the db.

@5chdn
Copy link
Contributor

5chdn commented Jan 4, 2018

@slavicd #6372

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
F3-annoyance 💩 The client behaves within expectations, however this “expected behaviour” itself is at issue. M4-core ⛓ Core client code / Rust.
Projects
None yet
Development

No branches or pull requests

6 participants