The bor snapshot prune-block command will prune historical blockchain data stored in the ancientdb. The amount of blocks expected for remaining after prune can be specified via block-amount-reserved in this command, will prune and only remain the specified amount of old block data in ancientdb.
The brief workflow as below:
- backup the the number of specified number of blocks backward in original ancientdb into new ancient_backup,
- then delete the original ancientdb dir and rename the ancient_backup to original one for replacement,
- finally assemble the statedb and new ancientdb together.
The purpose of doing it is because the block data will be moved into the ancient store when it becomes old enough (exceed the Threshold 90000), the disk usage will be very large over time, and is occupied mainly by ancientdb, so it's very necessary to do block data pruning, this feature will handle it.
Warning: This command only works with hash based storage scheme and doesn't work with path based storage scheme.
-
block-amount-reserved: Sets the expected reserved number of blocks for offline block prune (default: 1024) -
cache.triesinmemory: Number of block states (tries) to keep in memory (default = 128) (default: 128) -
check-snapshot-with-mpt: Enable checking between snapshot and MPT (default: false) -
datadir: Path of the data directory to store information -
datadir.ancient: Path of the old ancient data directory -
keystore: Path of the data directory to store keys
cache: Megabytes of memory allocated to internal caching (default: 1024)