Skip to content

[backport 3.2] box: flush WAL queue on sync#11329

Merged
sergepetrenko merged 1 commit intorelease/3.2from
backport/release/3.2/11315
Apr 3, 2025
Merged

[backport 3.2] box: flush WAL queue on sync#11329
sergepetrenko merged 1 commit intorelease/3.2from
backport/release/3.2/11315

Conversation

@TarantoolBot
Copy link
Collaborator

@TarantoolBot TarantoolBot commented Apr 3, 2025

(This PR is a backport of #11315 to release/3.2 to a future 3.2.2 release.)


wal_sync() is expected to flush all prepared txns on disk. Currently it is not so because we do not flush txns waiting in WAL queue. AFAIU the issue exists for all the places where we use wal_sync() (except for box_wait_limbo_acked() where we already flush WAL queue). The test is only added for the vinyl index build as there are explicit tickets for that.

Closes #11118
Closes #11119

`wal_sync()` is expected to flush all prepared txns on disk. Currently
it is not so because we do not flush txns waiting in WAL queue. AFAIU
the issue exists for all the places where we use `wal_sync()` (except
for `box_wait_limbo_acked()` where we already flush WAL queue). The test
is only added for the vinyl index build as there are explicit tickets for
that.

Closes #11118
Closes #11119

NO_DOC=bugfix

(cherry picked from commit af5f033)
@TarantoolBot TarantoolBot requested a review from a team as a code owner April 3, 2025 08:42
@TarantoolBot TarantoolBot changed the title [Backport release/3.2] box: flush WAL queue on sync [backport 3.2] box: flush WAL queue on sync Apr 3, 2025
@coveralls
Copy link

Coverage Status

coverage: 87.386% (-0.04%) from 87.428%
when pulling c5cf3cd on backport/release/3.2/11315
into 4a54362
on release/3.2
.

@sergepetrenko sergepetrenko merged commit 6f7e35a into release/3.2 Apr 3, 2025
23 of 24 checks passed
@sergepetrenko sergepetrenko deleted the backport/release/3.2/11315 branch April 3, 2025 10:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants