Quick question: For some reason, when I do a yum update or yum makecache fast on a newly deployed system our local mirror is almost never selected. It’s very strange because a) It’s a public mirror physically located on campus, so it’s closest and b) the mirror is run on a gigabit connection with a solid state hard drive. Does anyone have any ideas on why our local mirror is almost never choosen as one of the fastest available mirrors?
Hi Ryan,
You need to specify your local mirror in the yum.repos.d file for your on-site systems to force use your local mirror.
Regards, Christopher Hawker Phone: +61 419 273 141
________________________________ From: CentOS-mirror centos-mirror-bounces@centos.org on behalf of Ryan Nix ryan.nix@gmail.com Sent: Tuesday, 10 January 2017 4:35 AM To: Mailing list for CentOS mirrors. Subject: Re: [CentOS-mirror] How the mirrors work?
Quick question: For some reason, when I do a yum update or yum makecache fast on a newly deployed system our local mirror is almost never selected. It's very strange because a) It's a public mirror physically located on campus, so it's closest and b) the mirror is run on a gigabit connection with a solid state hard drive. Does anyone have any ideas on why our local mirror is almost never choosen as one of the fastest available mirrors? _______________________________________________ CentOS-mirror mailing list CentOS-mirror@centos.org https://lists.centos.org/mailman/listinfo/centos-mirror CentOS-mirror Info Pagehttps://lists.centos.org/mailman/listinfo/centos-mirror lists.centos.org To see the collection of prior postings to the list, visit the CentOS-mirror Archives. Using CentOS-mirror: To post a message to all the list members ...
On 09/01/17 18:35, Ryan Nix wrote:
Quick question: For some reason, when I do a yum update or yum makecache fast on a newly deployed system our local mirror is almost never selected. It’s very strange because a) It’s a public mirror physically located on campus, so it’s closest and b) the mirror is run on a gigabit connection with a solid state hard drive. Does anyone have any ideas on why our local mirror is almost never choosen as one of the fastest available mirrors?
There is no ASN/subnet checking but only GeoIP for country. The current code produces random lists with 10 validated mirrors, so your public mirror can be added, removed, added back in the yum mirrorlist multiple times a day (and the more mirrors in the same country, the less chances to be always referenced)