On Fri, 07 Sep 2012, Kohsuke Kawaguchi wrote: > > Jenkins handles a lot of download requests for core as well as > plugins. So we rely on our mirrors to actually deliver bits. > > Unfortunately, by the nature of our mirrors, there's some time lag > between the time we stage our master copy of files (which gets > created as a part of the update center metadata generation process) > to the time mirrors pick up those files. > > But as soon as bits are staged in the master copy, those URLs get > advertised (download link from http://jenkins-ci.org/ and update > center metadata.) Right now, download requests that happened during > this window will result in 404. > > What can we do to fix this? Does anyone have any thoughts?
Technically the OSUOSL mirror system is one we push to, I think we try to only
run rsync's on a poll based interval but there's no reason we can't "push"
more.
Both cabbage and lettuce have LVM-managed disks, so we should be able expand
those volumes if needed. MirrorBrain allows for setting a fallback mirror which
we currently set to the ftp-nyc OSUOSL mirror (IIRC). We can easily set that to
cabbage or lettuce if we chose those as a dedicated mirror master.
- R. Tyler Croy
--------------------------------------
Code: https://github.com/rtyler
Chatter: https://twitter.com/agentdero
signature.asc
Description: Digital signature
