aboutsummaryrefslogtreecommitdiffstats
path: root/docs/store.md
diff options
context:
space:
mode:
Diffstat (limited to 'docs/store.md')
-rw-r--r--docs/store.md20
1 files changed, 12 insertions, 8 deletions
diff --git a/docs/store.md b/docs/store.md
index a1d9c8c..ffca117 100644
--- a/docs/store.md
+++ b/docs/store.md
@@ -316,14 +316,17 @@ record (its ID, its coordinator): two remakes at one base are two epochs.
that its checkpoint forgot, as it read none of it in the old document.
* **A node that rejoins**, as it was away, lacks the base, or is on the higher of two
epochs, takes the epoch its peers give it, or the one its operator pins, as
- continuum's node rejoins. It keeps its own checkpoint and reads from the new document
- what is above its heads, judging every event; a later checkpoint the snapshot holds,
- which it can't build from what it holds, it takes only where its operator pins it
- (Pinned checkpoints). It puts again what the new document lacks, as after a switch.
- What its own refusals and its operator's drops refuse, it reads none of. A node with
- an empty document does the same, from the root its operator names or a checkpoint its
- operator pins. A made-up epoch can withhold events from it, and keep it apart from the
- others, but make it take nothing it wouldn't.
+ continuum's node rejoins, but only where the snapshot's checkpoint is its document's,
+ one it builds from that document, or one its operator pins: a snapshot holding an
+ earlier one would leave the new document holding events whose history nobody puts
+ again. It keeps its own checkpoint and reads from the new document what is above its
+ heads, judging every event; a later checkpoint the snapshot holds, which it can't
+ build from what it holds, it takes only where its operator pins it (Pinned
+ checkpoints). It puts again what the new document lacks, as after a switch. What its
+ own refusals and its operator's drops refuse, it reads none of. A node with an empty
+ document does the same, from the root its operator names or a checkpoint its operator
+ pins. A made-up epoch can withhold events from it, and keep it apart from the others,
+ but make it take nothing it wouldn't.
So a remake changes no event a node holds, only which document carries them, which the
fold never sees. A swarm that never remakes holds what one that remakes all the time
@@ -395,6 +398,7 @@ crafted changes. *Sim*: a simulation. *Bench*: measured, not judged.
| 28 | A remake whose base comes before a checkpoint, switched after nodes moved to it | They switch, keep their checkpoint, read none of what it forgot, and put again from the old document what a store starting at the snapshot's checkpoint takes to reach theirs | sim |
| 29 | Flooding: events, writers, history, remakes | Slow, or out of memory; not wrong | bench |
| 30 | A member decides compactions, grinding their IDs until the new epoch's ID is lower than the honest one's | Nodes on the honest epoch rejoin the lower, once a generation; no event is lost: slow, not wrong | sim |
+| 31 | A made-up epoch whose snapshot holds a checkpoint before the node's document's, the root say | Not followed: a node follows an epoch only where the snapshot's checkpoint is its document's, one it builds from it, or one its operator pins | sim |
## Tests