diff options
| author | tv <tv@krebsco.de> | 2026-11-19 16:13:53 +0000 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-19 17:35:42 +0100 |
| commit | 866c6a402e65f9102e63cebdf5a50c0a3f526260 (patch) | |
| tree | 8e3051bdebb3f136dee5bbcda1ad6de723b2f171 /docs/operations.md | |
| parent | 180e5ad1d1d144f5e9f9168094a0ec0417b64a61 (diff) | |
wire: a peer on another version is named older or newer, with what to upgrade
A node meeting messages of a wire version it doesn't speak logged
`Peer speaks another wire version (another build)`, with the versions
as fields only. It says now, in the message, which build is the newer
and which node to upgrade: this one, where the peer's is newer
(`upgrade this node to talk with it`), else the peer's
(`upgrade that node`), with the peer's version and the ones this build
speaks. Its fields are the peer's version and the oldest and newest this
build speaks.
Diffstat (limited to 'docs/operations.md')
| -rw-r--r-- | docs/operations.md | 17 |
1 files changed, 9 insertions, 8 deletions
diff --git a/docs/operations.md b/docs/operations.md index efc6b04..d100a49 100644 --- a/docs/operations.md +++ b/docs/operations.md @@ -128,13 +128,15 @@ A node upgrades by restarting with its files. What to know: * **The wire format.** Each change to it bumps a version byte, and nodes ignore messages of another version. Across such a change, upgraded nodes and the others don't talk: the swarm is split until every node is upgraded, both sides go on - writing, and they merge then. Each logs it (`Peer speaks another wire version - (another build); ignoring its messages`, warn, once per peer). With each handshake, a + writing, and they merge then. Each logs it, at warn, once per peer, naming both + versions and the node to upgrade (`Peer speaks another wire version: a newer build + (wire version 53; this one speaks 52): upgrade this node to talk with it; ignoring its + messages`, or of an older build, `upgrade that node`). With each handshake, a node says which versions it speaks, and the newest revision of the federation it knows (SPEAKS, outside the versions; [`peers.md`](peers.md), - [Handshake and join](peers.md#handshake-and-join)); a build from before SPEAKS logs it - as that warning, `version=0`, once of the peer, and reads the peer's other messages - where they are of its version. + [Handshake and join](peers.md#handshake-and-join)); a build from before SPEAKS, before + 0.0.1, logs it as another wire version, `version=0`, once of the peer, and reads the + peer's other messages where they are of its version. A node speaks one version, so every change of the format is a major release; before 1.0.0, take every upgrade as one, and upgrade all nodes close together. * **Automerge.** A remake needs every node to build the same snapshot, byte for byte, @@ -280,9 +282,8 @@ And from the log, at warn or error: * `Couldn't write the state file`, `Couldn't rewrite the document file`: a full or read-only disk; * `The … file is readable by others than its owner; chmod 600 it`; -* `Peer speaks another wire version (another build); ignoring its messages`: a node on - another build; with `version=0`, only a newer build's SPEAKS, which this build doesn't - read. +* `Peer speaks another wire version: …; ignoring its messages`: a node on another + build; the message names both versions, and whether to upgrade this node or that one. ## What a node uses |
