This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[routing-wg] Issue affecting rsync RPKI repository fetching
- Previous message (by thread): [routing-wg] Issue affecting rsync RPKI repository fetching
- Next message (by thread): [routing-wg] Issue affecting rsync RPKI repository fetching
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Nick Hilliard
nick at foobar.org
Mon Apr 12 15:12:10 CEST 2021
Erik Bais wrote on 12/04/2021 11:41: > This looks to be a 3 line bash script fix on a cronjob … So why isn’t > this just tested on a testbed and updated before the end of the week ? cache coherency and transaction guarantees are problems which are known to be difficult to solve. Long term, the RIPE NCC probably needs to aim for the degree of transaction read consistency that might be provided by an ACID database or something equivalent, and that will take time and probably a migration away from a filesystem-based data store. So the question is what to do in the interim? The bash script that Job posted may help to reduce some of the race conditions that are being observed, but it's unlikely to guarantee transaction consistency in a deep sense. Does the RIPE NCC have an opinion on whether the approach used in this script would help with some of the problems that are being seen and if so, would there be any significant negative effects associated with implementing it as an intermediate patch-up? Nick
- Previous message (by thread): [routing-wg] Issue affecting rsync RPKI repository fetching
- Next message (by thread): [routing-wg] Issue affecting rsync RPKI repository fetching
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]