Skip to content

Keep busy retained recovery from blocking unrelated batches (0.6) #666

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
hardbyte merged 2 commits into from
Nov 7, 2026
Merged

Keep busy retained recovery from blocking unrelated batches (0.6) #666

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
fce272e
Isolate retained recovery contention in rescue and completion batches
hardbyte Nov 7, 2026
59649b2
Keep completion contention fixtures from changing shared storage routing
hardbyte Nov 7, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 6 additions & 3 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -91,9 +91,12 @@ order; binaries can roll back to 0.6.13 with the patch retained. See the
perform that repair, and can leave an old replacement claimable. The aging
fence prevents new replacements from updated callers; it cannot fence an
older process explicitly calling physical aging during a rolling upgrade.
Repair takes claim-head row locks without waiting and rolls back on contention;
the operation must retry. It adds weak relation locks and tombstone writes
only on this recovery path. Fresh rechecks rely on READ COMMITTED isolation.
Repair takes claim-head row locks without waiting. Rescue batches defer
busy historical attempts while progressing other attempts; receipt rescue
cursors keep deferred attempts eligible. Worker completion batches isolate
lock contention to the affected requests. Direct completion and
single-attempt mutations still fail on contention and must retry. It adds
weak relation locks and tombstone writes only on this recovery path. Fresh rechecks rely on READ COMMITTED isolation.

## [0.6.13] — 2026-11-06

Expand Down
Loading
Loading