Re: mirrorlist server selection

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 3/17/2010 4:14 PM, Seth Vidal wrote:


So you have to maintain 2 things in sync instead of just one, and
since every host behind a cache is likely to choose a different mirror
name you end up downloading 10 copies of every update - or however
many mirrors there are.

a different mirror name? What are you talking about.

You don't keep 2 things in sync - you just keep one - don't use the
round robin at all.

ONLY use the mirrorlists.

Doesn't the mirrorlist refer to the DNS names? So if you add, delete, or move a mirror you'd have to update DNS for its name, then put the DNS name in your mirrorlist - and you have two things that can get out of sync, both cached in various places.

since yum is the thing that has to access the repos/pkgs only the
mirrorlist matters.

So each host behind a squid picks a name from the list and since they are likely different names, squid won't know the target url is already in its cache. And getting/managing copies of the mirrorlist is much slower than a new DNS lookup. There's probably a rare case where being able to 'yum clean all' on demand is quicker than waiting for an intermediate DNS cache to refresh and clear a bad entry, but things have gone badly wrong if you need that.

--
  Les Mikesell
   lesmikesell@xxxxxxxxx

_______________________________________________
Yum mailing list
Yum@xxxxxxxxxxxxxxxxx
http://lists.baseurl.org/mailman/listinfo/yum

[Index of Archives]     [Fedora Users]     [Fedora Legacy List]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]

  Powered by Linux