Hi Wesley, Le 26.08.2010 à 20:41, Wesley Haines a écrit : > >> One thing I note is that the wrpn mirror seems to send all requests to >> openoffice.cs.utah.edu. I don't know why it does that - it should >> certainly be not that way, because we already send requests directly >> to openoffice.cs.utah.edu. Thus, I will disable the >> openoffice.mirror.wrpn.net mirror for the time being. >> >> Who knows, maybe some problems were found at their end and they worked >> around this way. I am adding Wesley to Cc who administers the mirror; >> I guess he'll know more. [The best procedure to get rid of requests is >> to let us know here on the list, because we can disable them at any >> time.] > > Hi Peter, > > You're correct... some time ago, probably before the new mirror system > was put into place, we were getting hundreds of download requests per > minute. This was mainly for the Windows downloads. They were going quite > slowly because of the number of simultaneous connections. I set up a > redirect to send those requests elsewhere so that the existing downloads > wouldn't be tied up. It looks like I forgot to remove that redirect, and > the rsync script never removed it either when it synchronized the > directories.
Thanks for taking the time and explaining it! > For now, please leave our mirror disabled. We're bringing in a new fiber > line for the rack where the mirror server is hosted. I will also add a Fine! > round-robin entry for "openoffice.mirror.wrpn.net" to add a secondary > mirror server. DNS round robin is not optimal, because it leaves potential for things going wrong. A detailed explanation of the issues can be found here: http://mirrorbrain.org/archive/mirrorbrain/0042.html But in short, the issue is that the mirror servers could have different content at times, and then it's not good to treat them as one (which DNSrr does). Feel free to use DNSrr anyway, if you want for other reasons; I'd just ask you for the favour to arrange a DNS name for each server, so we can address them individually. Then we can scan them separately and send them requests separately. That solves all our problems with DNSrr (and you still can use DNSrr at the same time, for whatever purpose). You don't have to fear floods of requests (for OpenOffice.org downloads) in the future. The mirror URLs themselves are not published in ways that attract heavy traffic; everything goes through download.services.openoffice.org, and redirection can be stopped at any time. Also, the load balancing that assigns requests to your mirror works reliably and we can tune it to send you as few or as much traffic as you want to handle. > I apologize for causing any issues. I'll let you know when we are ready > to enable the mirror again. This didn't cause any problems. The only thing that could have happened is that the mirror in utah might have gotten too many requests (because it got your share as well). But I didn't hear any complaints :-) Thank you very much for taking the time for talking about this, and your hard work! Best regards, Peter --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
