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

Snapshot sync is started from scratch after restart #6415

Closed
akandratovich opened this issue Aug 29, 2017 · 5 comments
Closed

Snapshot sync is started from scratch after restart #6415

akandratovich opened this issue Aug 29, 2017 · 5 comments
Labels
F3-annoyance 💩 The client behaves within expectations, however this “expected behaviour” itself is at issue. M4-core ⛓ Core client code / Rust. P5-sometimesoon 🌲 Issue is worth doing soon.
Milestone
2.1 Whatever

Comments

@akandratovich
Copy link

I'm starting new parity node with empty state. Snapshot sync in progress. When I restart node, all synced snapshots are ignored and counter starts from zero.

Does snapshot sync has some disk state?
@5chdn 5chdn added F3-annoyance 💩 The client behaves within expectations, however this “expected behaviour” itself is at issue. M4-core ⛓ Core client code / Rust. Z0-unconfirmed 🤔 Issue might be valid, but it’s not yet known. labels Aug 30, 2017
@5chdn
Copy link
Contributor

5chdn commented Aug 30, 2017

Slightly related to #6350.

I'm not entirely sure how the snapshot sync works in this case. Did you restart the node immediately? Or was there some time passing between stopping and starting the node? It's quite possible that the client started fetching a new snapshot and therefore started from scratch.

@5chdn 5chdn added the P7-nicetohave 🐕 Issue is worth doing eventually. label Sep 4, 2017
@BreezeRo
Copy link

BreezeRo commented Sep 4, 2017

This just occurred to me running 1.7.0 on docker

@5chdn
Copy link
Contributor

5chdn commented Sep 5, 2017

@BreezeRo Did you restart the node immediately? Or was there some time passing between stopping and starting the node?

@5chdn 5chdn added P5-sometimesoon 🌲 Issue is worth doing soon. and removed P7-nicetohave 🐕 Issue is worth doing eventually. labels Sep 5, 2017
@akandratovich
Copy link
Author

@5chdn In my case - few seconds, maybe minute

@5chdn 5chdn added this to the 1.9 milestone Oct 5, 2017
@5chdn 5chdn mentioned this issue Nov 30, 2017
Closed
@5chdn 5chdn removed the Z0-unconfirmed 🤔 Issue might be valid, but it’s not yet known. label Jan 3, 2018
@5chdn 5chdn modified the milestones: 1.9, 1.10 Jan 5, 2018
@5chdn 5chdn modified the milestones: 1.10, 1.11 Jan 23, 2018
@5chdn 5chdn modified the milestones: 1.11, 1.12 Mar 1, 2018
@5chdn 5chdn modified the milestones: 1.12, 1.13 Apr 24, 2018
@5chdn 5chdn mentioned this issue May 7, 2018
Merged
@5chdn
Copy link
Contributor

5chdn commented May 16, 2018

Fixed in #8544

@5chdn 5chdn closed this as completed May 16, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
F3-annoyance 💩 The client behaves within expectations, however this “expected behaviour” itself is at issue. M4-core ⛓ Core client code / Rust. P5-sometimesoon 🌲 Issue is worth doing soon.
Projects
None yet
Milestone
2.1 Whatever
Development

No branches or pull requests
3 participants
@akandratovich @BreezeRo @5chdn