diff options
| author | tv <tv@krebsco.de> | 2026-11-18 20:08:28 +0000 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-18 21:17:40 +0100 |
| commit | 79614926332977718956f35e1adf80ae67e219f1 (patch) | |
| tree | 011d1b66381233f61f04c77360e1f9f8f704c5c6 /docs/store.md | |
| parent | 8369d2ef1ce1f5856cbff2bd33b1c39dfe80e445 (diff) | |
store: a stopped node leaves out none of what it holds back
A store that stopped can't tell which of what it holds back will be taken, nor which of
what waits: `Store::held_back` gives both, each after what it builds on. A node leaves
out none of it: it puts it again where its document lacks it (`Holding::lacking`), a
remake's snapshot holds it (`Holding::at_base`), and after a switch or a rejoin it puts
again what of it the document it left held (`Holding::left`). A remake while nodes are
stopped no longer drops what was put since the stop, nor the event they stopped at.
Tested: a node keeps what it holds back, what waited among it, through a snapshot, and a
store read anew from that stops there again; and a simulation: a swarm stopped at a
version compacts, a node away meanwhile rejoins and one started again with nothing reads
the new epoch, each stopping there, holding back what came after, until their operators
have them drop that event.
Diffstat (limited to 'docs/store.md')
| -rw-r--r-- | docs/store.md | 32 |
1 files changed, 19 insertions, 13 deletions
diff --git a/docs/store.md b/docs/store.md index b598539..ad98f9f 100644 --- a/docs/store.md +++ b/docs/store.md @@ -216,10 +216,13 @@ a fold knowing more reads (the federation's node: a version event writing a vers that passed, which its continuum doesn't read, [Changing the federation](federation.md#changing-the-federation)). The node takes nothing and refuses nothing from then on: it holds back whatever comes, that event first, -keeps none of it across a restart, where it stops there again, and reports it, until it +keeps none of it in its file, as a restart stops there again, and reports it, until it runs a continuum that reads the event, or its operator has it drop the event, or one it -builds on. Then it refuses it, as dropped or as built on what was, with everything built -on it, and judges what it held back. What it took before it stopped, it holds as it did. +builds on. Then it refuses that event, as dropped or as built on what was, with +everything built on it, and judges what it held back. What it took before it stopped, it +holds as it did. Of what it holds back, and what waits, it leaves out none, as it can't +tell which will be taken: it puts it again where its document lacks it, and a remake's +snapshot holds it ([Remakes](#remakes)). ## Forks @@ -308,11 +311,12 @@ a restart. **A node puts again**, in changes of its own, every event its document lacks that a store starting at the document's checkpoint would take, but for the node's own refusals and drops, and that the node has: one it holds, one in a change it refused, or one the -document it left held, at a switch or a rejoin ([Remakes](#remakes)). It puts each after -its dependencies, once a short wait of its own has passed, random, so that not every node -puts the same, and none another node put meanwhile. Each event is taken again as it was: -its history is there too. Continuum still refuses some changes on its own, by what they -are or who wrote them: of a writer's two changes of one number, the second +document it left held, at a switch or a rejoin ([Remakes](#remakes)); and, where its store +stopped, what it holds back and what waits ([A node's own](#a-nodes-own)). It puts each +after its dependencies, once a short wait of its own has passed, random, so that not +every node puts the same, and none another node put meanwhile. Each event is taken again +as it was: its history is there too. Continuum still refuses some changes on its own, by +what they are or who wrote them: of a writer's two changes of one number, the second ([Where Automerge sets limits](#where-automerge-sets-limits)); what such a change carried still reaches the store, and the documents those two changes part hold the same events. And no remake leaves out an event a store starting at the new document's checkpoint takes. @@ -348,14 +352,16 @@ coordinator): two remakes at one base are two epochs. * **The snapshot** holds the store a node reads from the document up to the base, starting at the document's checkpoint, by its own refusals and drops: the checkpoint it reaches there, where it isn't the root, the events that one keeps and those after - it, each at its ID; the policy; and of continuum's protocol data what a compaction - carries, but the entries of nodes that aren't members at the base. What that + it, and, where the store stops there, what it holds back and what waits, as it can't + tell which will be taken ([A node's own](#a-nodes-own)), each at its ID; the policy; + and of continuum's protocol data what a compaction carries, but the entries of nodes + that aren't members at the base. What that checkpoint forgot, and events nobody takes, leave the document here. A node that moved to a later checkpoint since the base builds the snapshot as one that didn't, as both read the document; nodes that read the store differently at the base (the sides of - keys that voted twice, in the federation, or a node that stopped, holding back what - the others took: [A node's own](#a-nodes-own)) build different snapshots, and part - here. + keys that voted twice, in the federation, or a node that stopped, where the others + refuse, or still wait for, some of what it holds back) build different snapshots, and + part here. * **A node follows a decision** whichever node coordinated it: a decision reaches it only through a member, which could decide one itself, and a remake changes no event. It builds the snapshot itself, from a base it holds, and checks it against the |
