On Fri, Mar 19, 2010 at 03:44:29PM -0400, Seth Vidal wrote: > On Thu, 18 Mar 2010, Adrian Reber wrote: > >> I am not sure I formulated my problem correctly, so I have written a >> patch that does what I want. Maybe this helps to describe my problem >> better. To test it I have created a DNS entry (mirrors.lisas.de) which >> points to four IPs: >> >> $ host mirrors.lisas.de >> mirrors.lisas.de has address 129.143.116.10 >> mirrors.lisas.de has address 134.108.44.54 >> mirrors.lisas.de has address 88.198.59.188 >> mirrors.lisas.de has address 129.143.116.9 >> >> Two of those entries are working mirrorlists, one has a webserver which >> does know nothing about mirrorlist and returns a 404 (129.143.116.10) and one >> does not even have anything running on port 80 (129.143.116.9). I am >> using following repo file: >> > > okay so why don't you remove the 2 broken ones from dns and your problem > goes away? Like Ljubomir said, it is for simulating what would happen if one of the mirrorlist servers has crashed. If the whole system has crashed or only the python wsgi doing the mirrorlist. Goal is it to make it more robust for failures in the mirrorlist infrastructure. > or better yet - just have a single non-round-robin'd url for the > mirrorlist itself. To better distribute the load (or in case one server is not reachable) the users should still get a working mirrorlist server. This is just like in Fedora's setup where it resolves to four IP addresses. In RPM Fusion's case it is only two servers, but in case one is not reachable my idea is that instead that the user gets an error it automatically uses the second mirrorlist server. Adrian _______________________________________________ Yum mailing list Yum@xxxxxxxxxxxxxxxxx http://lists.baseurl.org/mailman/listinfo/yum
