Skip to content

Conversation

@paritytech-release-backport-bot

Backport #9868 into unstable2507 from AndreiEres.

See the documentation on how to use this bot.

# Description

During statement store benchmarking we experienced deadlock-like
behavior which we found happened during statement propagation. Every
second statements were propagating, locking the index which possibly
caused the deadlock. After the fix, the observed behavior no longer
occurs.

Even though there is a possibility to unsync the DB and the index for
read operations and release locks earlier, which should be harmless, it
leads to regressions. I suspect because of concurrent access to many
calls of db.get(). Checked with the benchmarks in
#9884

## Integration

This PR should not affect downstream projects.

---------

Co-authored-by: cmd[bot] <41898282+github-actions[bot]@users.noreply.github.com>
(cherry picked from commit ed4eebb)
@github-actions github-actions bot added the A3-backport Pull request is already reviewed well in another branch. label Sep 30, 2025
@github-actions github-actions bot requested a review from AndreiEres September 30, 2025 23:19
Copy link
Contributor

@gui1117 gui1117 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure we want to backport fix on the node for unstable2507 but the PR is good.

@paritytech-workflow-stopper
Copy link

All GitHub workflows were cancelled due to failure one of the required jobs.
Failed workflow url: https://github.com/paritytech/polkadot-sdk/actions/runs/18707260149
Failed job name: test-linux-stable

@acatangiu
Copy link
Contributor

not needed, this branch is just for published crates, there are no node releases coming from this branch

@acatangiu acatangiu closed this Oct 22, 2025
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.

4 participants