aboutsummaryrefslogtreecommitdiffstats
path: root/src
Commit message (Collapse)AuthorAgeFilesLines
...
* nodes prefer stable neighbourstv11 days1-10/+89
|
* assess swarm stabilitytv12 days8-11/+330
|
* record RTT sampling instanttv12 days4-30/+104
|
* prefer closer sources to catch uptv12 days3-3/+49
|
* record RTT from keepalive messagestv12 days7-20/+148
|
* pull missing changestv12 days7-5/+162
| | | | | | Nodes push changes to their neighbours but don't relay them directly. In a partial mesh, nodes can learn about missing changes via keepalive messages and can pull them from their neighbours.
* find reachable neighbourstv12 days3-55/+162
|
* sync with neighbourstv12 days6-4/+171
|
* add neighbour graphtv12 days2-0/+180
|
* add member registrytv12 days4-1/+73
|
* use nonce in handshaketv12 days5-2/+39
| | | | | To prevent stale hello replies to cause joins and thus stale sessions, each run gets a random ID, which used as nonce in the handshake.
* drain queued messages on startuptv12 days1-2/+48
|
* consolidate backoff codetv12 days4-49/+99
|
* retry using fresh messagestv12 days3-170/+180
| | | | | Don't store encoded messages but retry using a newly generated one. That way any accumulated changes can be delivered at once.
* heal from noticed divergencetv12 days1-6/+27
| | | | | Wait 2*keepalive but at least 20 s to trigger resync so that lost messages can be resent first.
* heal after reply timeouttv12 days1-0/+3
|
* drop stall breaker; resend needed changestv12 days2-82/+21
| | | | | | The stall breaker was superseded by regular re-handshaking Re-handshaking also gets triggered, when a node needs some of the heads its peer believes it has already sent. In that case the peer now resends what's needed.
* no heal during catch-uptv12 days1-1/+6
|
* peers that just became ready get syncstv12 days1-0/+9
| | | | | | When keepalive says ready and we didn't have taht on record before, the peer is queued for sync. Hello and hello reply don't do this because the handshake already queues a sync.
* both sides may open sync after resettv12 days6-163/+64
| | | | | | | | | | Ready nodes will leave the first message to the pear that isn't ready. Hello and hello reply now carry ready, so readiness is known from the very first contact, before any sync. Together with the sync messages and keepalives, reports_ready is always current. After epoch switch, pings go to everyone except ready members already on the new epoch, these learn from the lagging peer's opening.
* perform handshake in one round triptv12 days6-85/+74
|
* drop pre-membership sync messagestv12 days4-47/+10
| | | | | The handshake resets the session anyway, and the sender's reply timeout resends what still matters.
* bump number of heads in keepalive messagestv12 days5-11/+94
| | | | | Instead of arbitrarily limiting the number to 16, allow filling keepalive messages as long as they don't cause mycelium to chunk it.
* probe sync source during catch-uptv12 days4-109/+28
| | | | This allows changing sources without the fixed 30 s stall duration.
* enrich keepalive contenttv12 days5-44/+307
| | | | | | | Add ready and syncs_with_you flags as well as actual heads, so the peer - ready: same meaning as in the sync message - syncs_with_you: sender counts recipient as member and in same epoch - heads: allows to tell who's behind or if both sides have changes
* use only ready peers as sync sourcetv12 days4-11/+65
| | | | | | Sync messages now carries a ready flag, telling whether the sending peer itself is joined or is itself still (re-)joining. In the latter case, the peer won't be used as sync source.
* catch up with a single source onlytv12 days3-1/+102
|
* introduce announce opening varianttv12 days1-6/+14
| | | | | This prevents a fall back to the 3 s grace period if a reset happens between the epoch switch and our opening went out.
* record the cause that started a sync sessiontv12 days3-12/+74
|
* merge sync_reset_at and epoch_unannounced into openingtv12 days3-56/+67
|
* introduce sync sessiontv12 days4-109/+124
| | | | SyncSession holds all fields that get reset by reset_sync()
* merge membership and authenticate into standingtv12 days5-43/+47
|
* announce epochs by sync instead of pingtv12 days2-4/+33
|
* pick pair leader by hash instead of key ordertv12 days5-4/+83
|
* ping only from one sidetv12 days2-3/+22
|
* allow changing log filtering while node runstv12 days4-1/+97
| | | | This also changes the default to tracing-subscriber.
* consistently use the words node, peer, and seedtv12 days7-12/+18
|
* open sync only from one sidetv12 days2-3/+45
| | | | | | | | | If both sides open, the openings cross, and an empty node's answer to the other opening (empty heads) makes the other side send the whole document a second time. Now after a sync reset, only the side with the smaller public key opens the sync; the other answers it, or opens itself if nothing arrives.
* don't resend sync messages to up-to-date peerstv13 days3-9/+34
| | | | | | | | | | | When an sync messages arrives and automerge has nothing to say about it, then no reply is generated. With c9279e4 it was assumed that every sync message gets an answer, so missing replies caused unnecessary resends. Now a reply is only awaited if the peer's last reported heads differ from ours. If the peer's heads become equal through a third peer without replying, the waiting will also abort if a ping or pong showss the same heads digest on both sides.
* introduce pre-shared swarm keytv13 days7-1/+316
|
* rename cluster to swarm everywhere!tv2026-10-2114-177/+162
|
* make remake switch delay configurabletv2026-10-213-2/+44
|
* install signal handlers early & handle SIGTERMtv2026-10-212-17/+58
|
* handle SIGTERMtv2026-10-211-0/+11
|
* let linux signal supervised mycelium when we dietv2026-10-211-8/+22
|
* resend sync messages that haven't been repliedtv2026-10-213-6/+90
|
* add the replace kind of remaketv2026-10-214-4/+256
| | | | | | | | | | | | | | POST /admin/remakes accepts specs with replace kind, e.g.: { "kind": "replace", "baseHeads": ["..."], "spec": { "document": { "accounts": { ... } }, "rules": [ { "from": "users", "to": "accounts" }, { "from": "users/admin", "drop": true }, { "from": "", "to": "" } ] } }
* allow choosing the base in remakestv2026-10-212-5/+54
| | | | | | | | | POST /admin/remakes accepts "baseHeads": ["<hex>", ...], for example the heads of an earlier GET /store?heads=true. Every head must be in the coordinating node's document, otherwise the request gets a 400. Without it, the base is the current heads. This works for any kind.
* add heads to readstv2026-10-212-9/+67
| | | | | | | | | | GET /store?heads=true and GET /store/{key}?heads=true add the header x-continuum-heads (sorted, comma-separated hex). The heads come from the same moment as the read. - It's opt-in because reading the heads takes the write lock. Reads without the flag don't change. - Stale reads during a rejoin never carry heads.
* turn compaction into a kind of remaketv2026-10-219-72/+589
|