Multi-instance: shared move marks for open editor documents (S3 write-fence residual) #1191

Open
opened 2026-11-21 17:41:26 +00:00 by Cordy · 0 comments
Owner

Follow-up of #742 (batch 10 R2-Q4; batch 11b spec-742b2b S3 residual).

Since v0.6.413 editor sessions are shared records and follow a rename, move or delete made on any member. The short-lived move marks that fence a save racing a move stay per member, so on S3 a save landing on another member in the moment of a move can write to the old path. Documented in multi-instance.md, Known limitations.

Goal: move marks as expiring shared records (the <prefix>_auth bucket, sealed under editor-table), read by the WOPI save path on every member, with a test racing a save on one member against a move on another.

Follow-up of #742 (batch 10 R2-Q4; batch 11b spec-742b2b S3 residual). Since v0.6.413 editor sessions are shared records and follow a rename, move or delete made on any member. The short-lived move marks that fence a save racing a move stay per member, so on S3 a save landing on another member in the moment of a move can write to the old path. Documented in multi-instance.md, Known limitations. Goal: move marks as expiring shared records (the `<prefix>_auth` bucket, sealed under `editor-table`), read by the WOPI save path on every member, with a test racing a save on one member against a move on another.
Sign in to join this conversation.
No labels
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Cordy/Cairn#1191
No description provided.