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/guides/federation/when-things-go-wrong.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/guides/federation/when-things-go-wrong.md')
| -rw-r--r-- | docs/guides/federation/when-things-go-wrong.md | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/docs/guides/federation/when-things-go-wrong.md b/docs/guides/federation/when-things-go-wrong.md index 8c46e1d..b59b69b 100644 --- a/docs/guides/federation/when-things-go-wrong.md +++ b/docs/guides/federation/when-things-go-wrong.md @@ -91,7 +91,10 @@ curl -u tv:secret -X POST -H 'Content-Type: application/json' \ ``` Allowed again (`/admin/events/allow`), it stops there once more. A node that stopped -keeps none of it in its store file: restarted, it stops there again. +keeps none of it in its store file: restarted, it stops there again. What it holds back +it leaves out of nothing, as it can't tell which will be taken: it puts it again where its +document lacks it, and a remake keeps it, so a remake while nodes are stopped loses none +of what was put since. ## A node doing less than it should |
