Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "b9v07"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Several instances, preview (#742 Step 1 batch A, #1011 Wave B)
Cairn can run as 3 or 5 instances that share one storage. A single instance (local mode) is unchanged apart from what CHANGELOG "Changed, read this before upgrading" lists.
Coordination
CAIRN_COORD_*variable.State
coord-unavailableandcluster-maintenance. Reads keep working, and/readyzstays green.Cluster lifecycle
cairnd migrate --to nats/--to local, with the U4 rule.cluster rescue,cluster certs [--ca], andcluster status, all over the admin socket.Key rotation
cairnd cluster reseal.cluster-keys-decidedandcluster-resealed.Observability
Kubernetes and docs
Verification
Follow-ups: #1176, #1177, #1178, #1179 (batch B and later). Known limitations are in
docs/handbook/multi-instance.md.internal/coord/natscoord: records in <prefix>_coord (history 1, file, Replicas 1/3/5, MaxValue + 64 KiB, markers 1 min, direct allowed); Get and every CAS check read from the stream leader (STREAM.MSG.GET); Create and Update are raw publishes with the expected subject sequence, Update carrying the stored Nats-TTL; Delete purges with a 1 min marker TTL; coord.NewLeases on the records; Notify on <prefix>.n.<topic>; member records instance.<KeyPart> with a 7-day TTL renewed per heartbeat; Log on stream <prefix>_log_<name>. Every call under min(caller, CallTimeout) (listings ReadTimeout); timeouts, no responders, closed connections, 10008 and 10005 wrap coord.ErrUnavailable. 10164 (wrong last sequence, constant) is retried within the deadline, not mapped to ErrConflict: nats-server 2.15.3 acks a write before it clears the subject's in-process mark (applyStreamMsgOp), so a CAS right after an ack can meet it (Leases/Exclusive50 on 3 nodes: Release "version changed"). The reference driver mapped it to a conflict. Mutants (must fail): go test -tags natscoord_mutant_kvupdate -run TTLSurvivesUpdate742a --- FAIL: TestTTLSurvivesUpdate742a (0.51s) natscoord742a_test.go:88: after update 1 the record's Nats-TTL is 0s, want 2s FAIL github.com/nikolasomborski/cairn/internal/coord/natscoord 0.513s go test -tags natscoord_mutant_shortttl -run InstancesLiveByHeartbeatAge742a --- FAIL: TestInstancesLiveByHeartbeatAge742a (0.71s) natscoord742a_test.go:432: member record Nats-TTL 1s, want 7 days FAIL github.com/nikolasomborski/cairn/internal/coord/natscoord 0.714s