we do something similar to what you're describing (on a fairly good scale):<br><br>most of the content in our databases comes from XML quasi-continuously streamed over persistent tcp sessions to parsing daemons that transform it into DML (~25M DML/day) on the replication master(s). we restart the listeners daily more or less for the hell of it though they have accidentally gone weeks w/o restarting w/o incident (someone forgot they commented out cronned restart).<br>
<br>I don't think there's a "one size fits all" answer to this ? - it depends on your volume, reliability of your network and fault tolerance of the code (/drivers/libraries) used at both ends. for us it's been insanely reliable though I'll admit a few years ago I pulled the XML/SQL translation back from the datacenter(s) to our office (i.e. only MySQL replication goes over WAN now). it wasn't that it was UNreliable before, just that MySQL replication is actually even MORE network fault tolerant (at least in our case).<br>
<br>if I had it to do all over (& I didn't design the current XML implimentation, just the DB replication) I would push the XML over persistent (but easily resetable) HTTP sessions to a load balancer (VIP) w/multiple active-active parallel ingestors behind it but our current design, while far from perfect, has been way more than reliable enough to justify "fixing" it...<br>
<br><div class="gmail_quote">On Wed, Mar 4, 2009 at 12:46 PM, Robert Reese~ <span dir="ltr"><<a href="mailto:ale@sixit.com">ale@sixit.com</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;">
<div class="im">> Quick poll/question.<br>
> Assume you have a daemon that talks to another daemon across a<br>
> network over a socket. The communication is constant and unlike<br>
> http requests are always alive. These socket connections would be<br>
> across a multimile geographic area but within a corporate WAN.<br>
> How often would you expect a connection would need to be restarted<br>
> before you decide that the connection is unstable. hours,<br>
> weeks,months? Please don't say seconds.<br>
<br>
</div>1^(10^100) seconds. Or until one side dies. In theory, anyway.<br>
<div><div></div><div class="h5"><br>
_______________________________________________<br>
Ale mailing list<br>
<a href="mailto:Ale@ale.org">Ale@ale.org</a><br>
<a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
</div></div></blockquote></div><br>