-
Notifications
You must be signed in to change notification settings - Fork 689
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
StateDb does not have PRUNING_MODE #821
Comments
I have faced the same issue. My node was previously synced with the flag
Reverting binary to previous version |
Sadly there was a bug before and the code is now more strict. You would need to resync with warp sync on 0.9.22. Sorry for the inconvenience! |
Okay, there is a problem with warp sync as well: paritytech/polkadot#5556 |
I started syncs from scratch for paritydb and rocksdb. |
@bkchr we are syncing since yesterday for Polkadot and Kusama. Kusama seems a bit slower, but Polkadot is way slower and is syncing only with ~8-15 bps. The specs of the VMs are the same as for the Validators (also pass the benchmark tests). |
@tugytur What parameters do you run your node with? |
@bkchr the only differences are the chain and db.
Kusama with paritydb is synced after almost 48h Polkadot with paritydb after ~50h |
This is fixed. |
* updated packages * remove after rebase * updated cumulus
When upgrading a node from 0.9.21 to 0.9.22 I get the following error on startup:
Also tried again with
--unsafe-pruning \
, issue is still thereThe text was updated successfully, but these errors were encountered: