Multi-instance: inbound peering state in NATS (drop the client-address affinity) #1189

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

Follow-up of #742 (batch 11b spec-742b2b S2/S14 non-goals, research-b11-r9 N13).

Today, with several instances, inbound peering transfers need client-address affinity at the load balancer: the peering state (peering.json, peer-transfers.json, the peer-blobs/ staging) is per instance. Documented in multi-instance.md, Known limitations.

Goal: move peering state into the coordination store (record per peer and per transfer, sealed, with leases where one member must act) and staging into the shared backend, so any member accepts any part of an inbound transfer, and drop the affinity row from the docs.

Same playbook as the uploads (v0.6.412) and sign-in records (v0.6.413): research, decisions, spec, build, VM run.

Follow-up of #742 (batch 11b spec-742b2b S2/S14 non-goals, research-b11-r9 N13). Today, with several instances, inbound peering transfers need client-address affinity at the load balancer: the peering state (`peering.json`, `peer-transfers.json`, the `peer-blobs/` staging) is per instance. Documented in multi-instance.md, Known limitations. Goal: move peering state into the coordination store (record per peer and per transfer, sealed, with leases where one member must act) and staging into the shared backend, so any member accepts any part of an inbound transfer, and drop the affinity row from the docs. Same playbook as the uploads (v0.6.412) and sign-in records (v0.6.413): research, decisions, spec, build, VM run.
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#1189
No description provided.