summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* add per peer incident statstv41 hours4-4/+52
|
* expose stats via the APItv42 hours2-0/+136
| | | | GET /admin/stats to retrieve all stats.
* add swarm statstv42 hours9-1/+238
|
* add traffic countertv42 hours9-12/+270
| | | | | | | | | | 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 neighbourstv42 hours1-10/+89
|
* assess swarm stabilitytv42 hours8-11/+330
|
* add tokio-console feature (fixup)tv43 hours1-1/+4
|
* edition = "2024" (fixup)tv43 hours1-1/+1
|
* record RTT sampling instanttv43 hours4-30/+104
|
* prefer closer sources to catch uptv43 hours3-3/+49
|
* record RTT from keepalive messagestv43 hours7-20/+148
|
* pull missing changestv43 hours7-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 neighbourstv44 hours3-55/+162
|
* sync with neighbourstv44 hours6-4/+171
|
* add neighbour graphtv44 hours2-0/+180
|
* add member registrytv44 hours4-1/+73
|
* use nonce in handshaketv45 hours5-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 startuptv45 hours1-2/+48
|
* consolidate backoff codetv45 hours4-49/+99
|
* retry using fresh messagestv45 hours3-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 divergencetv45 hours1-6/+27
| | | | | Wait 2*keepalive but at least 20 s to trigger resync so that lost messages can be resent first.
* heal after reply timeouttv47 hours1-0/+3
|
* drop stall breaker; resend needed changestv48 hours2-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-uptv2 days1-1/+6
|
* peers that just became ready get syncstv2 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 resettv2 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 triptv2 days6-85/+74
|
* drop pre-membership sync messagestv2 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 messagestv2 days6-11/+1069
| | | | | 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-uptv2 days4-109/+28
| | | | This allows changing sources without the fixed 30 s stall duration.
* enrich keepalive contenttv2 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 sourcetv2 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 onlytv2 days3-1/+102
|
* introduce announce opening varianttv2 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 sessiontv2 days3-12/+74
|
* merge sync_reset_at and epoch_unannounced into openingtv2 days3-56/+67
|
* introduce sync sessiontv2 days4-109/+124
| | | | SyncSession holds all fields that get reset by reset_sync()
* merge membership and authenticate into standingtv2 days5-43/+47
|
* announce epochs by sync instead of pingtv2 days2-4/+33
|
* pick pair leader by hash instead of key ordertv2 days5-4/+83
|
* ping only from one sidetv2 days2-3/+22
|
* allow changing log filtering while node runstv3 days4-1/+97
| | | | This also changes the default to tracing-subscriber.
* consistently use the words node, peer, and seedtv3 days7-12/+18
|
* open sync only from one sidetv3 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 peerstv3 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 keytv3 days7-1/+316
|
* rename cluster to swarm everywhere!tv4 days14-177/+162
|
* make remake switch delay configurabletv4 days3-2/+44
|
* install signal handlers early & handle SIGTERMtv4 days2-17/+58
|
* handle SIGTERMtv4 days1-0/+11
|