Prune data during blocksync#3
Conversation
26f2d93 to
0d9bd93
Compare
This enables pruning of cometbft db instances during initial block sync (starting either from the checkpoint or genesis). Cherry-picked from commit (cometbft/cometbft: db26cff) and resolved the conflicts: * Changelog was removed. * Where applicable `ApplyVerifiedBlock` was used.
0d9bd93 to
3988ee5
Compare
|
CI failing:
This properties can be removed, and then we can fix the linting issues. There are also some failing test that I think were there before -> will double check again now that I changed the code. Not sure we should fix this given this problems are also part of the upstream branch? Changelog: Update: |
|
Upstream is EOL AFAIK. |
Needed for oasisprotocol/oasis-core#6319.
Tested this quickly with state sync and block sync from the genesis (short period). Works.
Seems to also work as a mitigation for badgerDB instances growing too much and not being able to reclaim the disk space: oasisprotocol/oasis-core#6286 (comment).