summaryrefslogtreecommitdiffstats
path: root/src/swarm
Commit message (Collapse)AuthorAgeFilesLines
* cache headstv24 hours3-6/+11
| | | | To reduce the number of write locks, heads are now cached.
* being caught up needs some headstv25 hours1-5/+9
| | | | | | | | | | | A sync message from a ready peer only completes the initial sync if that peer has at least one head. A peer with an empty document can no longer make a joiner ready on an empty store: a misconfigured second swarm, or a genesis node in its first seconds. Effect on a brand-new swarm: a joiner now waits until the genesis node has registered itself in the member list, which happens within about 5 s of it becoming ready.
* put remake content into blobstv26 hours1-4/+21
|
* add chunked download and use it during rejointv28 hours5-1/+502
|
* add electoratetv31 hours1-8/+101
| | | | | For an upcoming change in remake coordination, nodes now maintain their self-assessed liveness in the document.
* aliases are not in logs (fixup)tv31 hours1-1/+1
|
* measure document saved-size only after changestv32 hours1-17/+39
|
* add endpoint to export the documenttv37 hours1-0/+9
| | | | GET /admin/document to retrieve the automerge document.
* add node aliasestv38 hours1-11/+78
|
* add throughput statstv38 hours4-1/+192
|
* add propagation statstv38 hours2-0/+89
|
* add swarm statstv38 hours7-1/+235
|
* add traffic countertv39 hours1-0/+4
| | | | | | | | | | This introduces a new wrapper that counts messages and payload bytes per peer, split by kind (hello, helloReply, sync, ping, pong), each sent, received and refused. The traffic counter goes around the firewall, which means messages dropped outbound are still counted as sent, and messages dropped inbound don't count as received.
* nodes prefer stable neighbourstv39 hours1-10/+89
|
* assess swarm stabilitytv39 hours4-11/+321
|
* record RTT sampling instanttv39 hours2-27/+95
|
* prefer closer sources to catch uptv40 hours1-3/+42
|
* record RTT from keepalive messagestv40 hours4-14/+130
|
* pull missing changestv40 hours5-5/+159
| | | | | | 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 neighbourstv40 hours2-55/+132
|
* sync with neighbourstv40 hours3-4/+142
|
* add neighbour graphtv41 hours2-0/+180
|
* add member registrytv41 hours3-0/+69
|
* use nonce in handshaketv41 hours1-2/+14
| | | | | 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.
* consolidate backoff codetv41 hours1-29/+15
|
* retry using fresh messagestv42 hours1-158/+127
| | | | | Don't store encoded messages but retry using a newly generated one. That way any accumulated changes can be delivered at once.
* drop stall breaker; resend needed changestv44 hours1-65/+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-uptv45 hours1-1/+6
|
* peers that just became ready get syncstv45 hours1-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 resettv45 hours3-42/+28
| | | | | | | | | | 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 triptv46 hours3-78/+68
|
* drop pre-membership sync messagestv46 hours3-43/+10
| | | | | The handshake resets the session anyway, and the sender's reply timeout resends what still matters.
* bump number of heads in keepalive messagestv46 hours1-0/+1
| | | | | 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-uptv46 hours3-106/+14
| | | | This allows changing sources without the fixed 30 s stall duration.
* enrich keepalive contenttv46 hours2-26/+208
| | | | | | | 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 sourcetv47 hours1-11/+52
| | | | | | 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 onlytv47 hours1-1/+86
|
* record the cause that started a sync sessiontv48 hours2-6/+15
|
* merge sync_reset_at and epoch_unannounced into openingtv48 hours2-9/+3
|
* introduce sync sessiontv2 days2-27/+33
| | | | SyncSession holds all fields that get reset by reset_sync()
* merge membership and authenticate into standingtv2 days3-25/+18
|
* announce epochs by sync instead of pingtv2 days1-0/+4
|
* pick pair leader by hash instead of key ordertv2 days4-2/+81
|
* ping only from one sidetv2 days1-1/+2
|
* consistently use the words node, peer, and seedtv2 days2-4/+4
|
* open sync only from one sidetv3 days1-3/+21
| | | | | | | | | 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 peerstv3 days2-9/+28
| | | | | | | | | | | 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 keytv3 days3-0/+279
|
* rename cluster to swarm everywhere!tv4 days3-68/+65
|
* resend sync messages that haven't been repliedtv4 days2-6/+23
|
generated by cgit v1.3.1 (git 2.54.0) at 2026-10-25 18:33:06 +0000