Skip to content

Conversation

@uwiger
Copy link
Contributor

@uwiger uwiger commented Apr 27, 2023

See issue #3088

The most (only?) robust way to avoid database corruption during IO saturation is to run with the db_direct_access setting. This makes the rocksdb plugin use rocksdb transactions rather than mnesia transactions. This ensures atomicity in the case when writes are rejected due to congestion.

This is an initial push, partly to ensure that we don't forget to make this the detault.

{ok, true} ->
case AllStandalone of
[] ->
lager:debug("Enabling direct access for rocksdb", []),
Copy link
Member

Choose a reason for hiding this comment

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

INFO would be more appropriate IMO

@dincho
Copy link
Member

dincho commented May 2, 2023

A release note is somehow important for this change IMO, although it is BC

seanhinde
seanhinde previously approved these changes May 29, 2023
dincho
dincho previously approved these changes May 29, 2023
@uwiger uwiger dismissed stale reviews from dincho and seanhinde via 51dd269 June 16, 2023 13:29
@uwiger uwiger force-pushed the gh3088-make-direct-access-default branch from ac82a82 to 51dd269 Compare June 16, 2023 13:29
Copy link
Contributor

@ThomasArts ThomasArts left a comment

Choose a reason for hiding this comment

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

Looks ok to me

@hanssv hanssv merged commit b394868 into master May 22, 2024
@hanssv hanssv deleted the gh3088-make-direct-access-default branch May 22, 2024 08:02
@dincho dincho added kind/feature Issues or PRs related to a new feature kind/improvement and removed kind/feature Issues or PRs related to a new feature labels May 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants