This repository was archived by the owner on Nov 15, 2023. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 15, 2023. It is now read-only.
--blocks-pruning archive-canonical broken #13269
Description
Is there an existing issue?
- I have searched the existing issues
Experiencing problems? Have you tried our Stack Exchange first?
- This is not a support question.
Description of bug
./polkadot --tmp --chain kusama --state-pruning archive-canonical --no-hardware-benchmarks --no-telemetry
2023-01-29 22:14:30 ----------------------------
2023-01-29 22:14:30 This chain is not in any way
2023-01-29 22:14:30 endorsed by the
2023-01-29 22:14:30 KUSAMA FOUNDATION
2023-01-29 22:14:30 ----------------------------
2023-01-29 22:14:30 Parity Polkadot
2023-01-29 22:14:30 ✌️ version 0.9.37-645723987cf
2023-01-29 22:14:30 ❤️ by Parity Technologies <admin@parity.io>, 2017-2023
2023-01-29 22:14:30 📋 Chain specification: Kusama
2023-01-29 22:14:30 🏷 Node name: diligent-orange-7774
2023-01-29 22:14:30 👤 Role: FULL
2023-01-29 22:14:30 💾 Database: RocksDb at /tmp/substratePJsmzv/chains/ksmcc3/db/full
2023-01-29 22:14:30 ⛓ Native runtime: kusama-9370 (parity-kusama-0.tx19.au2)
2023-01-29 22:14:30 🔨 Initializing Genesis block/state (state: 0xb000…ef6b, header-hash: 0xb0a8…dafe)
Error:
0: UnknownBlock: State already discarded for 0xb0a8d493285c2df73290dfb7e61f870f17b41801197a149ca93654499ea3dafe
Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.
2023-01-29 22:14:30 👴 Loading GRANDPA authority set from genesis on what appears to be first startup.
--state-pruning archive works
Steps to reproduce
./polkadot --tmp --chain kusama --state-pruning archive-canonical --no-hardware-benchmarks --no-telemetry or other Substrate-based chains including parachains
Activity
[-]`--blocks-pruning archive-canonical` not working[/-][+]`--blocks-pruning archive-canonical` broken[/+]maciejnems commentedon Jan 30, 2023
Seems like this error comes from using
--state-pruning archive-canonical, so it is related to state pruning, not block pruning. From what i understand, in Substratearchive-canonicalis the default value for--blocks-pruning.We experienced the same problem, and there is also an issue for that here: #12824.
Polkadot-Forum commentedon Mar 9, 2023
This issue has been mentioned on Polkadot Forum. There might be relevant details there:
https://forum.polkadot.network/t/polkadot-release-analysis-v0-9-39/2277/1