Hello! You probably hit the architectural limits of single thread routing. Try BIRD 3 (alpha).
Also with this load, it's very much recommended to have a BIRD Support package to have us booked for resolving high load problems. It's a time-consuming and very fiddly job for experienced developers. Please see https://bird.nic.cz/en/commercial-services/ for more details, and/or contact me off-list for a customized quote. Happy routing! Maria On 29 February 2024 10:08:56 CET, "mx.avanttel.ru via Bird-users" <[email protected]> wrote: >hello my friend, all the peers lose their connection at once, at different >times, the server of 1500,000 networks and 3000000 routes, where to look for >what to adjust, I ask for help, the server itself does not fall, the service >does not fall either > > > >] >Feb 27 05:02:45 bgp-01 bird: bgpMSKIX: Error: Hold timer expired >Feb 27 05:03:29 bgp-01 bird: bgpRFET2: Error: Hold timer expired >Feb 27 05:03:36 bgp-01 bird: bgpGLFW: Error: Hold timer expired >Feb 27 05:03:40 bgp-01 bird: Kernel dropped some netlink messages, will resync >on next scan. >Feb 27 05:03:45 bgp-01 bird: bgpKOMP: Error: Hold timer expired >Feb 27 05:03:58 bgp-01 bird: I/O loop cycle took 5094 ms for 6 events >Feb 27 05:04:29 bgp-01 bird: bgpZap: Error: Hold timer expired >Feb 27 05:04:44 bgp-01 bird: bgpSAL: Received: Hold timer expired >Feb 27 05:04:56 bgp-01 bird: bgpRKN2: Received: Hold timer expired >Feb 27 05:04:56 bgp-01 bird: bgpFIT: Error: Hold timer expired >Feb 27 05:05:02 bgp-01 bird: bgpGLIX1: Error: Hold timer expired >Feb 27 05:05:05 bgp-01 bird: Kernel dropped some netlink messages, will resync >on next scan. >Feb 27 05:05:16 bgp-01 bird: bgpRFET1: Received: Hold timer expired >Feb 27 05:05:19 bgp-01 bird: bgpRKN1: Received: Hold timer expired -- Maria Matejka (she/her) | BIRD Team Leader | CZ.NIC, z.s.p.o.
