4 Commits

Include renames

Author	SHA1	Message	Date
clawbot	e5afd94a39	Take every down peer out of the table in one walk (closes #225) ... The prefix handler ran one PeerDown per peer, one after another. When the sessions of several peers went down together, their walks queued up. A returning full-table peer's messages stayed held back while the walks ahead of its own ran, and could reach the limit of 20,000. The table's PeersDown now takes several peers out of every prefix in one walk. One walk runs at a time. The next one takes every peer whose session went down since the previous one began. The doc of maxHeldBackMessages says how long a peer's messages are held back. The limit is now 150,000 messages, about 150 MiB. The status page shows how many messages each handler holds back. Model: opus-5-5	2026-11-02 23:10:09 +01:00
clawbot	a671b8a0b0	Give every IP lookup result the same fields (closes #200) ... Every result of /ip/, /ip/{addr} and /api/v1/ip/{ip} now has every field. A field without a value is null instead of left out, so an address with no live route has all its route and AS fields set to null. ptr is an empty list when there are no PTR names. Two new fields, num_origins and origin_asns, give how many origin ASes peers carry the netblock with, and which. The routing table's prefix summary now lists them. asn still names the origin that most peers carry. first_seen is null, no longer the zero time, when the database has not stored the netblock yet. Model: opus-5-5	2026-10-27 19:54:02 +01:00
clawbot	bac531c76d	Write the routing table every second and read it at startup (part of #122) ... The prefix handler applies each update to the routing table in memory as it handles it, sorted into announcements and withdrawals as for the live route tables. Each flush first writes at most 20,000 of the table's changed pairs, with every new peer; the rest follow in the next flushes. A failed write puts its changes and new peers back in the table. Stop makes one last flush, and logs the changed pairs left. Startup reads the table before the streamer connects, and logs its pairs, peers and time. The per-peer counts are a slice, so the read takes about a third less time. The health check's start period is 60 seconds, so a full table's read fits before upaas looks. Model: opus-5-5	2026-10-27 10:27:11 +01:00
clawbot	7a34a46c4d	Add internal/routetable, the routing table in memory (part of #122) ... A new package holds every prefix some peer carries. For each prefix and origin AS it keeps the set of peers that carry it, one bit per peer, and the two newest of their routes in full. It applies announcements, withdrawals and peers' sessions going down by the rule confirmed on the issue, and records which pairs changed for the database writes to come. It answers the IP lookup, an AS's prefixes, a prefix's origins, a sample of one mask length, and the counts the stats show. Nothing uses it yet. The peer sets use github.com/bits-and-blooms/bitset. The kept routes' times are held in order in github.com/google/btree, so the oldest and newest need no scan. Model: opus-5-5	2026-10-27 07:51:55 +01:00