Hi Jason, I don't know every detail, but my memory of it is the details that I gave you. You can find more in the list archives. There's a lot of history on things, such as why the repository directory structure moved from flat to hierarchical (the CPU costs of generating index.html pages was large). Ibiblio was the master host for central for many years, and they finally had to push back because the bandwidth use was so high. Sonatype took over primary hosting sometime after that.
It stands to reason that the 80/20 rule applies very well here, as most projects only use one version of a given library and do not change very often. Downloading 30 other versions of it, as well as 30 versions of hundreds of other projects that aren't ever used by a site (including sources) are what caused the general prohibition on doing this. All it takes is a few sites globally rsyncing and the aggregate bandwidth required to host central goes up by orders of magnitude. It's not a good use of scarce resources to cater to a few groups that can't get their IT department to install Nexus. I'm sure there's some community policy on when it's okay for rsyncing ibiblio, and that's probably why it's still there. Cheers, Brian On Apr 22, 2012, at 11:56 AM, Jason Pyeron wrote: >> -----Original Message----- >> From: Brian Topping >> Sent: Sunday, April 22, 2012 11:32 >> >> On Apr 22, 2012, at 10:26 AM, Jason Pyeron wrote: >> >>> 1. Is mirrors.ibiblio.org a good source for mirroring >> repo1.maven.apache.org? >>> 2. is there a strong reason not use rsync? >> >> Mirroring a repository like that is considered very bad form >> and will probably get your servers blacklisted. > > This caught me off guard. Is that not the point of ibiblio.org supporting > rsync? > We have a daily rsync set up with them for other projects. > >> >> I don't have the benefit of other posts you may have made on >> this subject, > > No other posts on this topic. > >> but unless you are hosting half the known world >> of developers, why wouldn't you just use a repository? > > The mirror team has bandwith management infrastructure inplace. They did not > want to modify their system to support Nexus for Nexus sake. We have a nexus > server on our dev lan already. Our dev lan does not have direct access to the > internet. > >> It >> makes things so much simpler with your builds since real >> world projects generally do not pull from just central. > > It was listed on the bandwidth report. > >> Having a half-dozen repositories in your build is a great way >> to have it constantly slow (and even slower at times when any >> one of those repositories is offline). Caching those >> repositories through Nexus insulates you from their downtime, >> without having to soak their bandwidth for files you will never use. > > I agree that the Nexus pull only when needed is nice. But there are other > concerns too. The real question is there a strong reason for not using rsync > other than use Nexus. > > > -- > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > - - > - Jason Pyeron PD Inc. http://www.pdinc.us - > - Principal Consultant 10 West 24th Street #100 - > - +1 (443) 269-1555 x333 Baltimore, Maryland 21218 - > - - > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > This message is copyright PD Inc, subject to license 20080407P00. > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
