summaryrefslogtreecommitdiffstats
path: root/src/swarm
Commit message (Collapse)AuthorAgeFilesLines
...
* avoid stalled sourcetv5 days1-2/+24
| | | | | | | | | | | | | A source given up for not answering our sync messages could become the source again straight away. Whoever asks first after the reset takes the role, and that's often the same peer, which would then stall for another delivery limit. Now, a stalled source isn't chosen again for one more delivery_limit. If it's the only candidate, catching up waits that long and then tries it again. Before, a retry with that peer couldn't have helped any sooner anyway: a source is only given up after a whole delivery limit without a sync message, and that clock restarts when it is chosen again.
* MYCELIUM_DELIVERY_LIMIT -> Timing::delivery_limittv5 days1-6/+3
|
* recompute neighbours whenever topology changestv5 days4-5/+40
|
* run peer worker when becoming readytv5 days1-0/+8
|
* newly added neighbour get a sync attempttv5 days1-3/+12
|
* add simulation testtv5 days1-1/+4
|
* require catch-up source to make progresstv5 days2-1/+92
|
* late messages don't flip peer's epoch backtv5 days3-12/+56
|
* allow to persist documenttv5 days1-22/+145
|
* add files module to consistently track statstv5 days3-91/+34
|
* warn about unresolvable seeds once; log successtv5 days1-7/+22
|
* add disk I/O statstv5 days3-24/+78
|
* add possibility to start with a documenttv5 days1-4/+61
| | | | The --recover-from option allows a node start with a given document.
* add state filetv5 days4-2/+222
| | | | | This allows storing the swarm ID and additionally discovered seeds, which prevents a formerly genesis node to start a new document.
* put swarm ID into the documenttv5 days1-3/+19
|
* add genesis flag and never give uptv5 days1-65/+87
| | | | | | | | | The --genesis flag has been introduced to start with a new document. This prevents restarts to accidentally start with a new document and accept reads/writes, causing a second swarm to appear. Additionally, bootstrapping doesn't timeout anymore as that's of no use for nobody.
* bound stable-hub degreetv6 days1-4/+46
| | | | | | Each stable member can be preferred at most by 4*k members. The budget is spent in key order, which is the same on every node, so the graph stays deterministic, symmetric and connected.
* coalesce announcementstv6 days1-2/+56
|
* cache headstv6 days3-6/+11
| | | | To reduce the number of write locks, heads are now cached.
* being caught up needs some headstv6 days1-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 blobstv6 days1-4/+21
|
* add chunked download and use it during rejointv6 days5-1/+502
|
* add electoratetv6 days1-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)tv6 days1-1/+1
|
* measure document saved-size only after changestv6 days1-17/+39
|
* add endpoint to export the documenttv6 days1-0/+9
| | | | GET /admin/document to retrieve the automerge document.
* add node aliasestv6 days1-11/+78
|
* add throughput statstv6 days4-1/+192
|
* add propagation statstv6 days2-0/+89
|
* add swarm statstv6 days7-1/+235
|
* add traffic countertv6 days1-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 neighbourstv7 days1-10/+89
|
* assess swarm stabilitytv7 days4-11/+321
|
* record RTT sampling instanttv7 days2-27/+95
|
* prefer closer sources to catch uptv7 days1-3/+42
|
* record RTT from keepalive messagestv7 days4-14/+130
|
* pull missing changestv7 days5-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 neighbourstv7 days2-55/+132
|
* sync with neighbourstv7 days3-4/+142
|
* add neighbour graphtv7 days2-0/+180
|
* add member registrytv7 days3-0/+69
|
* use nonce in handshaketv7 days1-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 codetv7 days1-29/+15
|
* retry using fresh messagestv7 days1-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 changestv7 days1-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-uptv7 days1-1/+6
|
* peers that just became ready get syncstv7 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 resettv7 days3-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 triptv7 days3-78/+68
|
* drop pre-membership sync messagestv7 days3-43/+10
| | | | | The handshake resets the session anyway, and the sender's reply timeout resends what still matters.