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

What makes a node a warp-sync node? #7951

Closed
phahulin opened this issue Feb 19, 2018 · 1 comment
Closed

What makes a node a warp-sync node? #7951

phahulin opened this issue Feb 19, 2018 · 1 comment
Labels
M4-core ⛓ Core client code / Rust. Z1-question 🙋‍♀️ Issue is a question. Closer should answer.
Milestone

Comments

@phahulin
Copy link
Contributor

phahulin commented Feb 19, 2018

I'm running:

  • Which Parity version?: 1.9.2
  • Which operating system?: Linux
  • How installed?: via binaries
  • Are you fully synchronized?: yes
  • Which network are you connected to?: sokol
  • Did you try to restart the node?: no

When connecting to our network, some nodes can be warp-synced from (you download snapshots first, then latest blocks), but others - can't (you start downloading blocks from 0). Why is it, what makes a node warp-syncable (pardon my french)? both nodes appear to be fully synced (at least they have the same height).

@5chdn 5chdn added Z1-question 🙋‍♀️ Issue is a question. Closer should answer. M4-core ⛓ Core client code / Rust. labels Feb 21, 2018
@5chdn 5chdn added this to the 1.10 milestone Feb 21, 2018
@5chdn
Copy link
Contributor

5chdn commented Feb 21, 2018

Warp-Sync is hardly possible on Ethereum anymore as the state is growing so fast. The issue you experience is pretty much summarized on our wiki:

https://paritytech.github.io/wiki/Known-Issues-Priorities

Key issues are #7863 and #7436 here: There are not enough nodes in the network providing recent snapshots.

We are working hard on solutions, but it looks very much like the future belongs to the light clients.

@5chdn 5chdn closed this as completed Feb 21, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
M4-core ⛓ Core client code / Rust. Z1-question 🙋‍♀️ Issue is a question. Closer should answer.
Projects
None yet
Development

No branches or pull requests

2 participants