Skip to content

Conversation

@paritytech-release-backport-bot

Backport #10495 into stable2512 from bkchr.

See the documentation on how to use this bot.

Recently we introduced a change that was always force compacting a
Rocksdb database when starting a node and after writing a lot of data.
We found out that force compacting a huge RocksDB of more than 600GB
takes quite some time (more than one hour) and this every time.

So, this pull request changes the compaction to only happen after warp
sync (and genesis) when we reset the state column to some given state.
This way we don't run it anymore on startup of the node and it should
fix the problems we have seen with archive nodes.

---------

Co-authored-by: cmd[bot] <41898282+github-actions[bot]@users.noreply.github.com>
(cherry picked from commit 5b0576c)
@github-actions github-actions bot added the A3-backport Pull request is already reviewed well in another branch. label Dec 3, 2025
@github-actions github-actions bot requested a review from bkchr December 3, 2025 18:13
@github-actions
Copy link
Contributor

github-actions bot commented Dec 3, 2025

This pull request is amending an existing release. Please proceed with extreme caution,
as to not impact downstream teams that rely on the stability of it. Some things to consider:

  • Backports are only for 'patch' or 'minor' changes. No 'major' or other breaking change.
  • Should be a legit fix for some bug, not adding tons of new features.
  • Must either be already audited or not need an audit.
Emergency Bypass

If you really need to bypass this check: add validate: false to each crate
in the Prdoc where a breaking change is introduced. This will release a new major
version of that crate and all its reverse dependencies and basically break the release.

@bkchr bkchr enabled auto-merge (squash) December 3, 2025 21:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A3-backport Pull request is already reviewed well in another branch.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants