S3 stores without CopyObject (OVH Local Zones): the record probe refuses to start Cairn #956

Closed
opened 2026-10-17 16:21:21 +00:00 by Cordy · 1 comment
Owner

Side finding from the #943 research (2026-10-17).

What happens:

  • Since v0.6.347, Cairn probes the S3 store at start: PUT, HEAD, then CopyObject with COPY and with REPLACE. If any step fails, Cairn refuses to start (s3: the record probe failed; refusing to start (#922)).
  • OVH's Local Zones object storage does not support CopyObject at all, according to OVH's documentation (see the research file for the source). Cairn therefore cannot run on such a store.
  • Cairn also relies on CopyObject for moves (copy then delete), for records in copy mode, and for snapshots.

Expected: decide whether Cairn supports stores without CopyObject. Two ways:

  • (a) Support them. The probe falls back to "put" mode for publishing. Moves and snapshots stream the object through Cairn (GET + PUT), which costs traffic but works.
  • (b) Refuse them on purpose. Cairn stops with a clear error that names the missing capability, and the docs list it as a requirement.

To do:

  • Decide (a) or (b).
  • Test with a fake store that answers CopyObject with 501.
  • Document the outcome in deployment.md, under "Records of saves".
Side finding from the #943 research (2026-10-17). **What happens:** - Since v0.6.347, Cairn probes the S3 store at start: PUT, HEAD, then CopyObject with COPY and with REPLACE. If any step fails, Cairn refuses to start (`s3: the record probe failed; refusing to start (#922)`). - OVH's Local Zones object storage does not support CopyObject at all, according to OVH's documentation (see the research file for the source). Cairn therefore cannot run on such a store. - Cairn also relies on CopyObject for moves (copy then delete), for records in copy mode, and for snapshots. **Expected:** decide whether Cairn supports stores without CopyObject. Two ways: - **(a) Support them.** The probe falls back to "put" mode for publishing. Moves and snapshots stream the object through Cairn (GET + PUT), which costs traffic but works. - **(b) Refuse them on purpose.** Cairn stops with a clear error that names the missing capability, and the docs list it as a requirement. **To do:** - Decide (a) or (b). - Test with a fake store that answers CopyObject with 501. - Document the outcome in deployment.md, under "Records of saves".
Author
Owner

Decision (Nikola, 2026-10-27): refuse such stores at start, with a named error that the store cannot copy objects server-side (no CopyObject). deployment.md lists the store requirements. No streaming fallback. Size S, planned for batch R4.

Background is in the C1 decision sheet: only OVH Local Zones are known to lack CopyObject (OVH Regions have it). A streaming GET+PUT path would cost 2 to 3 times the file size in traffic and add a permanent second code path.

**Decision (Nikola, 2026-10-27):** refuse such stores at start, with a named error that the store cannot copy objects server-side (no CopyObject). deployment.md lists the store requirements. No streaming fallback. Size S, planned for batch R4. Background is in the C1 decision sheet: only OVH Local Zones are known to lack CopyObject (OVH Regions have it). A streaming GET+PUT path would cost 2 to 3 times the file size in traffic and add a permanent second code path.
Cordy closed this issue 2026-10-27 12:22:52 +00:00
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#956
No description provided.