The machines are in geographically separate locations. <br><br>The reason for round-robin is both load balance and for fail-over. <br><br>My guess is more folks than you think have crazy infrastructure. :) I've got servers in 4 geographically separate locations for example. <br>
<br><br><div class="gmail_quote">On Fri, Oct 23, 2009 at 3:38 PM, J.H. <span dir="ltr"><<a href="mailto:warthog9@kernel.org">warthog9@kernel.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Speaking as someone who has machines in a round-robin (for a number of<br>
reasons) If the boxes are in the same place (same colo, etc) I would<br>
suggest daisy chain syncing.<br>
<br>
msync -> box 1 -> box 2<br>
<br>
it will mean that box2 will always lag, slightly, behind box 1 but it<br>
means less load on the upstream and I would doubt if your users are<br>
going to notice much.<br>
<br>
If you have disjoint machines (like I do), than having each one sync<br>
independently is the only real answer, though I can't imagine there are<br>
many mirrors who fall into my category of crazy infrastructure.<br>
<br>
What is the reason your doing round robin between the two? Have you<br>
considered a shared storage solution if they are in the same place, I.E.<br>
sync to a "master" backend and push the changes to the two frontends?<br>
<br>
I guess to make good suggestions, comments, etc (beyond the incredibly<br>
generic things) we are going to need to know more about why you have<br>
this setup and what your trying to do / accomplish with it.<br>
<br>
- John 'Warthog9' Hawley<br>
Chief Kernel.org Administrator<br>
<div class="im"><br>
Nick Olsen wrote:<br>
> Well whats the point of the round robin? To distribute load between the<br>
> two boxes, and cover fail over?<br>
> To save bandwidth from everyone's point of view I think it would be<br>
> better to sync one from msync, and sync the other one from the first<br>
> one. What does everyone else think?<br>
><br>
> On 10/23/2009 3:22 PM, Bob Bownes wrote:<br>
>> Dedup....indeed.<br>
>><br>
>> So do I need to do anything special if I am going to have two machines<br>
>> (in disparate locations) on a round robin DNS answering to<br>
</div>>> <a href="http://mirror.seiri.com" target="_blank">mirror.seiri.com</a> <<a href="http://mirror.seiri.com" target="_blank">http://mirror.seiri.com</a>> (and rsyncing from msync)<br>
<div class="im">>><br>
>> I could sync one from the other, but that kinda defeats the round<br>
>> robin point.<br>
>><br>
>> iii<br>
>><br>
>><br>
>><br>
>><br>
>> 2009/10/23 João Carlos Mendes Luís <<a href="mailto:jonny@jonny.eng.br">jonny@jonny.eng.br</a><br>
</div>>> <mailto:<a href="mailto:jonny@jonny.eng.br">jonny@jonny.eng.br</a>>><br>
<div class="im">>><br>
>> That's why we really need block level deduplication, ASAP... ;-)<br>
>><br>
>> Jeff Sheltren wrote:<br>
>> > On Oct 23, 2009, at 10:22 AM, Nick Olsen wrote:<br>
>> ><br>
>> ><br>
>> >> Never Thought of that....<br>
>> >> I guess your right.<br>
>> >> Don't really see why ISO's shouldn't be carried though.<br>
>> >><br>
>> ><br>
>> > Disk space.<br>
>> ><br>
>> > Some people (I won't name names, *cough* warthog *cough*) might<br>
>> argue<br>
>> > that having ISO images is simply a replication of the packages we're<br>
>> > already carrying on the mirror and that there should be a better way<br>
>> > to handle stuff so that mirrors don't end up with multiple copies of<br>
>> > what is essentially the same data.<br>
>> ><br>
>> > -Jeff<br>
>> > _______________________________________________<br>
>> > CentOS-mirror mailing list<br>
</div>>> > <a href="mailto:CentOS-mirror@centos.org">CentOS-mirror@centos.org</a> <mailto:<a href="mailto:CentOS-mirror@centos.org">CentOS-mirror@centos.org</a>><br>
<div class="im">>> > <a href="http://lists.centos.org/mailman/listinfo/centos-mirror" target="_blank">http://lists.centos.org/mailman/listinfo/centos-mirror</a><br>
>> ><br>
>> _______________________________________________<br>
>> CentOS-mirror mailing list<br>
</div>>> <a href="mailto:CentOS-mirror@centos.org">CentOS-mirror@centos.org</a> <mailto:<a href="mailto:CentOS-mirror@centos.org">CentOS-mirror@centos.org</a>><br>
<div><div></div><div class="h5">>> <a href="http://lists.centos.org/mailman/listinfo/centos-mirror" target="_blank">http://lists.centos.org/mailman/listinfo/centos-mirror</a><br>
>><br>
>><br>
>><br>
>> _______________________________________________<br>
>> CentOS-mirror mailing list<br>
>> <a href="mailto:CentOS-mirror@centos.org">CentOS-mirror@centos.org</a><br>
>> <a href="http://lists.centos.org/mailman/listinfo/centos-mirror" target="_blank">http://lists.centos.org/mailman/listinfo/centos-mirror</a><br>
>><br>
><br>
> ------------------------------------------------------------------------<br>
><br>
> _______________________________________________<br>
> CentOS-mirror mailing list<br>
> <a href="mailto:CentOS-mirror@centos.org">CentOS-mirror@centos.org</a><br>
> <a href="http://lists.centos.org/mailman/listinfo/centos-mirror" target="_blank">http://lists.centos.org/mailman/listinfo/centos-mirror</a><br>
<br>
_______________________________________________<br>
CentOS-mirror mailing list<br>
<a href="mailto:CentOS-mirror@centos.org">CentOS-mirror@centos.org</a><br>
<a href="http://lists.centos.org/mailman/listinfo/centos-mirror" target="_blank">http://lists.centos.org/mailman/listinfo/centos-mirror</a><br>
</div></div></blockquote></div><br>