唐小鸭 6c37ebb951 fix(replication): address a replicated marker purge by the target's version id (backlog#2290) ...

A source-side DELETE ?versionId=<marker> replicates as a version purge, and
replicate_delete_to_target addressed it by the SOURCE marker id on every
target. A generic S3 target answers a DELETE of an unknown versionId with
204 and keeps its marker, so the purge reported success and the marker
stayed; the same event also spawned a second delayed-purge watcher that
journaled a duplicate intent. Real VMs (R6.1 in backlog#2080) failed on the
persisted-id fix alone because this path never consulted the mapping.

Resolve the target version through the recorded mapping for marker purges
(a corrupt record refuses, as the watcher does; nothing recorded keeps the
source-derived id for id-mirroring peers), and do not spawn the delayed
watcher for a version purge — that purge is the replication itself and its
failures reach the journal as a purge entry.

2026-09-05 19:40:40 +08:00

..

src

fix(replication): address a replicated marker purge by the target's version id (backlog#2290)

2026-09-05 19:40:40 +08:00

tests

test(replication): add mixed-version MRF acceptance matrix (#5673)

2026-08-03 22:09:59 +08:00

Cargo.toml

feat: extend hotpath coverage across crates (#5505)

2026-07-31 05:42:19 +00:00