<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On 27 February 2014 06:44, Carlos Carvalho <span dir="ltr"><<a href="mailto:carlos@fisica.ufpr.br" target="_blank">carlos@fisica.ufpr.br</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">If you want to experiment with what gives best performance, fine. If<br>
you just want to make sure updates work well it's better to limit<br>
access to tier 1 mirrors only. That's the whole point of tiering. I<br>
prefer this option.<br>
<br>
We update every hour but check the timestamp of fullfilelist and only<br>
do the dreadful scan when it's changed, so there's no impact on the<br>
server. All mirrors that deserve access to the tier 0's should do the<br>
same...<br>
<br></blockquote><div><br></div><div>Could you share your scripts on how you do this? Every mirror has a different way of doing things because they mirror so many different servers but showing best practices might help others to do similar things.</div>
<div><br></div><div> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Stephen John Smoogen (<a href="mailto:smooge@gmail.com">smooge@gmail.com</a>) wrote on 26 February 2014 09:11:<br>
<div class=""> >When trying to do the mirrors on local disks we got better in some<br>
>stats but were running into problems with keeping up with failed<br>
>disks<br>
<br>
</div>The number of disks in the handful tier-0 mirrors is small enough<br>
(<~20) to be perfectly feasible to have them local.<br>
<div class=""><br></div></blockquote><div><br></div><div>We aren't just serving the tier 0 servers. We are the default http access for everyone who can't find a mirror or hard codes to using us. We also serve packages for various engineering tasks internally which makes local storage non-scalable. We could drop rsync to only tier 0/1 mirrors. However, from the large number of mirrors that hit us directly it would break a lot of people and I want to make sure I announce it, double announce it, slashdot it, etc so that when the inevitable "Fedora is dropping mirrors" stories come out it is clear why and how mirrors not following the tier process should work now.</div>
<div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">
>keeping stuff in sync (box x out of n would always not get y package when the<br>
>others and that would be the one server every dns picks).<br>
<br>
</div>You have to trigger them from the master to avoid updates while the<br>
repository is changing. If you monitor the update results from each<br>
mirror you can, even automatically, pull out of the dns list the one<br>
that didn't complete well.<br>
<br>
It IS feasible to have mirrors with local disks. Other distros do it.<br><br></blockquote><div><br></div><div>I didn't say it wasn't feasible and I know other distros do it.. I worked with the CentOS guys for a while. It just isn't how we have been set up for 8+ years so we have a lot of assumptions in place around it.</div>
</div><br><br clear="all"><div><br></div>-- <br><div dir="ltr">Stephen J Smoogen.<br><br></div>
</div></div>