This repository has been archived by the owner on Nov 6, 2020. It is now read-only.
Parity Ropsten upgrade from 2.1.10 to 2.2.8 restarts syncing from genesis block #10275
Labels
Z7-duplicate 🖨
Issue is a duplicate. Closer should comment with a link to the duplicate.
Milestone
Comments
jam10o-new
added
the
Z7-duplicate 🖨
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I had deployed and fully synced a Parity Ropsten node version 2.1.10 with the
--pruning=archiveoption.It finished syncing a few days ago and is currently at the latest Ropsten block - the same block that ropsten.etherscan.io shows (currently 4936368).
However, I'm trying to upgrade to the latest version of Parity (2.2.8), but when I upgrade the node to version 2.2.8, it starts syncing from the genesis block instead of reusing the existing state.
In the past when I upgraded the Parity version it would reuse the old state and keep syncing - in the worst case it would re-org the bad blocks, but with the latest version it seems to create a new state trie and starts syncing from the beginning.
The text was updated successfully, but these errors were encountered: