[routing-wg] rsync://rpki.ripe.net rsyncd limits set too low?
- Previous message (by thread): [routing-wg] rsync://rpki.ripe.net rsyncd limits set too low?
- Next message (by thread): [routing-wg] RFO for RIPE NCC RPKI outage 16 February 2022
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Job Snijders
job at fastly.com
Wed Feb 16 15:52:49 CET 2022
Hi Ties, Thank you for the quick reply. On Wed, Feb 16, 2022 at 03:32:06PM +0100, Ties de Kock wrote: > Ouch. Fallback to rsync due to a DNS misconfiguration (which should > have recovered). Thanks for the confirmation. Indeed, my monitors seem to have returned to 'all clear'. > There are multiple instances behind a load-balancer. The current > storage is on NFS which has a performance limitation - it peaked at > about 80K operations/second (2m average). Welp! That's a lot of IO. Sharing from my own experience with a tiny publication point: I estimate there are about 4,000 RPs deployed on the Internet. Assuming their synchronisation attempts are evenly distributed across the hour, a naieve calculation suggests every single second a new client will attempt to connect. > We will follow up with a more detailed post-mortem. Much appreciated! Kind regards, Job
- Previous message (by thread): [routing-wg] rsync://rpki.ripe.net rsyncd limits set too low?
- Next message (by thread): [routing-wg] RFO for RIPE NCC RPKI outage 16 February 2022
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]