Registry
Each registration is independent. The witness holds no shared state between clusters and cannot be used to correlate them.
| Cluster | Consensus | Voters | Witness role | Registered | Elections |
|---|---|---|---|---|---|
| atlas-euPrimary ledger | Raft | 3 | arbiter | 2024-03-11 | 18 |
| ledger-fraTransaction log | Raft | 4 | arbiter | 2024-06-02 | 41 |
| meridianConfiguration store | Multi-Paxos | 3 | arbiter | 2024-09-19 | 6 |
| parcel-nlRouting table | Raft | 2 | tie-break | 2025-01-27 | 203 |
| vaultlineKey custody | Raft | 5 | arbiter | 2025-05-14 | 3 |
| stillwaterArchive index | Raft | 3 | standby | 2026-02-08 | 0 |
Send the cluster name, consensus flavour and the number of voting members. We issue a member identifier and a shared secret; the identifier goes into your membership configuration as an ordinary non-voting learner that is then promoted to voter.
Clusters with an even voter count get the most out of this: parcel-nl has two voters and would deadlock on every partition without a third opinion. Its 203 elections are almost entirely tie-breaks.
Odd-sized clusters use the witness differently — as insurance against losing a whole site rather than as a tie-breaker. vaultline has held three elections in fifteen months.
Demote the witness to learner, wait one lease period, then remove it from the configuration. Detaching without demotion is safe but noisy: the cluster will log a lost member for one election timeout.
Member identifiers are not reused. A detached cluster that returns later gets a new one, so old decisions can never be replayed against it.