Our current MySQL configuration has two servers in active-active state
(ie, neither is a master, both are fully active and serving requests).
The MySQL servers use a Network Appliance for storage.<br>
<br>
Regards,<br>
Paul<br><br><div><span class="gmail_quote">On 5/30/05, <b class="gmail_sendername">Jiri Kuthan</b> <<a href="mailto:jiri@iptel.org">jiri@iptel.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
At 03:40 AM 5/30/2005, Java Rockx wrote:<br>>Currently, usrloc is replicated via t_replicate() using db_mode=writeback.<br>><br>>However,
our lazy-load patch would obsolete the need for t_replicate() because
we have multiple MySQL servers that are active-active so __all__
replication really occurs at the database layer rather than the SIP
layer.<br><br>So this is the point which I am still struggling with. I mean generally there is a problem<br>of read-write intenstive UsrLoc operations. We can move it from SIP to DB. However, whichever<br>layer we choose to solve the problem, it takes careful dimensioning. Otherwise the
<br>replication mechanism may cause peformance problems.<br><br>What Mysql setup are you exactly using? Cluster? Master/slave replication?<br><br>Otherwise I think that the cache policy "load-on-demand" makes sense.
<br><br>-jiri<br><br></blockquote></div><br>