summaryrefslogtreecommitdiffstats
path: root/src/swarm
Commit message (Collapse)AuthorAgeFilesLines
* allow humand-friendly durations and sizes in CLItv2 days2-2/+2
|
* SyncSessions owns Automerge's sync statetv2 days2-80/+12
|
* unify keepalivetv2 days1-15/+23
|
* split peer moduletv2 days9-915/+995
|
* unify peers snapshot logictv2 days1-11/+3
|
* unify lock logictv2 days10-70/+31
|
* move protocol paths to dedicated moduletv2 days3-7/+7
|
* refresh peers after stalltv3 days2-1/+19
|
* add random swarms testtv3 days1-0/+62
|
* add clock moduletv3 days3-6/+11
| | | | | The Clock module is the system clock that every unix timestamp new goes through. It comes with an offset that only tests can set.
* avoid stalled sourcetv3 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_limittv3 days1-6/+3
|
* recompute neighbours whenever topology changestv3 days4-5/+40
|
* run peer worker when becoming readytv3 days1-0/+8
|
* newly added neighbour get a sync attempttv3 days1-3/+12
|
* add simulation testtv3 days1-1/+4
|
* require catch-up source to make progresstv3 days2-1/+92
|
* late messages don't flip peer's epoch backtv3 days3-12/+56
|
* allow to persist documenttv3 days1-22/+145
|
* add files module to consistently track statstv3 days3-91/+34
|
* warn about unresolvable seeds once; log successtv3 days1-7/+22
|
* add disk I/O statstv3 days3-24/+78
|
* add possibility to start with a documenttv3 days1-4/+61
| | | | The --recover-from option allows a node start with a given document.
* add state filetv3 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 documenttv3 days1-3/+19
|
* add genesis flag and never give uptv3 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 degreetv4 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 announcementstv4 days1-2/+56
|
* cache headstv4 days3-6/+11
| | | | To reduce the number of write locks, heads are now cached.
* being caught up needs some headstv4 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 blobstv4 days1-4/+21
|
* add chunked download and use it during rejointv4 days5-1/+502
|
* add electoratetv4 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)tv4 days1-1/+1
|
* measure document saved-size only after changestv4 days1-17/+39
|
* add endpoint to export the documenttv4 days1-0/+9
| | | | GET /admin/document to retrieve the automerge document.
* add node aliasestv4 days1-11/+78
|
* add throughput statstv4 days4-1/+192
|
* add propagation statstv4 days2-0/+89
|
* add swarm statstv4 days7-1/+235
|
* add traffic countertv4 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 neighbourstv4 days1-10/+89
|
* assess swarm stabilitytv4 days4-11/+321
|
* record RTT sampling instanttv4 days2-27/+95
|
* prefer closer sources to catch uptv4 days1-3/+42
|
* record RTT from keepalive messagestv4 days4-14/+130
|
* pull missing changestv4 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 neighbourstv4 days2-55/+132
|
* sync with neighbourstv4 days3-4/+142
|
* add neighbour graphtv4 days2-0/+180
|