On Thu, Feb 4, 2010 at 14:40, Dieter Plaetinck <dieter@xxxxxxxxxxxx> wrote: > On Thu, 4 Feb 2010 14:27:14 -0500 > Lee Burton <lburton@xxxxxxxx> wrote: > >> To make it "multi-tiered" and to reduce load on the primary mirror >> could have slightly more intelligent polling than just checking one >> upstream machine. >> In this example Let: >> Primary = Arch Primary Mirror/Mirrors (updated directly by the >> dbscripts). Tier-1 = Large High-Bandwidth/Traffic mirrors that other >> mirrors mirror off of Tier-2 = Smaller mirrors >> It would then go something like: >> A tier-1 mirror would check against the Primaries once a minute (for >> the md5sum). >> A tier-2 mirror would check against two tier-1 mirrors and see if they >> agree, if they don't it would ask a primary for a tie-break. It would >> then could notify (via an automated email?, perhaps one in a 24-hour >> period? if it's been out of date for XX hours) the mirror owner of the >> out of date mirror? > > seems needlessly complex to me. > Dieter > It probably is. Perhaps a push-primary solution (much simpler..) combined with a default twice a day sync (just to make sure?) for tier-1 mirrors might work.. the I believe point here is to get ideas out there. -- Lee Burton lburton@xxxxxxxx 301 910 0246
