You're going to have all sorts of data concurency problems doing any of this. Think about what happens as you get failures on one box and you start using the other.. The data will change on one and not the other.. then the primary comes back up.<div>
<br></div><div>You really need a DB failover solution and clustering is really the right way to do it.. I did this with MySQL Master/Slave replication for years. Although it works, there are still problems using the backup mysql server. Namely, you can't really be entirely sure it's accurate data. And then when the primary comes back online, you'll have CDR in the backup that isn't in the primary. All sorts of problems like that..</div>
<div><br></div><div>Now if you are just doing something simple like LCR routes, or simple lookups that are static, consider using something like dbtext instead as it doesn't need a mysql running process to operate.</div>
<div><br></div><div>That's my $0.02. I'm sure there are others that used the master/slave type replication with success, but I think it's less than ideal. Just remember, it will look like a *perfect* solution for you, until you get a DB failure.</div>
<div>-Brett</div><div><br></div><div><br><div class="gmail_quote">On Tue, Nov 25, 2008 at 8:20 AM, Matteo D'Amato <span dir="ltr"><<a href="mailto:matteo@ecosma.com">matteo@ecosma.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div lang="EN-US" link="blue" vlink="purple">
<div>
<p><span style="font-size:11.0pt;color:#1F497D">With SRV, if one box is down will it still get hit or does the
DNS only send to the one that is up?</span></p>
<p><span style="font-size:11.0pt;color:#1F497D"> </span></p>
<p><span style="font-size:11.0pt;color:#1F497D"> </span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p><b><span style="font-size:10.0pt">From:</span></b><span style="font-size:10.0pt">
<a href="mailto:users-bounces@lists.opensips.org" target="_blank">users-bounces@lists.opensips.org</a> [mailto:<a href="mailto:users-bounces@lists.opensips.org" target="_blank">users-bounces@lists.opensips.org</a>] <b>On
Behalf Of </b>Pablo Hernan Saro<br>
<b>Sent:</b> Tuesday, November 25, 2008 8:04 AM<br>
<b>To:</b> Krunal Patel<br>
<b>Cc:</b> <a href="mailto:users@lists.opensips.org" target="_blank">users@lists.opensips.org</a><br>
<b>Subject:</b> Re: [OpenSIPS-Users] Help!! How to do failover of mysql
connection</span></p>
</div><div><div></div><div class="Wj3C7c">
<p> </p>
<p style="margin-bottom:12.0pt">That will not work. Try DNS
SRV. Take a look at this link <a href="http://www.zytrax.com/books/dns/ch8/srv.html" target="_blank">http://www.zytrax.com/books/dns/ch8/srv.html</a><br>
Hope it helps.<br>
<br>
Pablo</p>
<div>
<p>On Tue, Nov 25, 2008 at 2:51 AM, Krunal Patel <<a href="mailto:krunal.lists@gmail.com" target="_blank">krunal.lists@gmail.com</a>> wrote:</p>
<p>Hi,<br>
<br>
is it fine if I use DSN resolver?<br>
Let me explain in detail:<br>
I setup a DSN resolver & add A record for mysql servers.<br>
mysql
A <a href="http://192.168.1.5" target="_blank">192.168.1.5</a><br>
mysql
A <a href="http://192.168.1.6" target="_blank">192.168.1.6</a><br>
<br>
where <a href="http://192.168.1.5" target="_blank">192.168.1.5</a> & <a href="http://192.168.1.6" target="_blank">192.168.1.6</a> are mysql cluster
nodes.<br>
<br>
So <a href="http://mysql.somedomain.com" target="_blank">mysql.somedomain.com</a>
will point to both servers.<br>
It will do load balance & failover both.<br>
<br>
Please confirm that it will not create any issue.<br>
<br>
Thanks,<br>
<span style="color:#888888">Krunal Patel</span></p>
<div>
<div>
<p style="margin-bottom:12.0pt"> </p>
<div>
<p>On Tue, Nov 25, 2008 at 1:35 AM, Geoffrey Mina <<a href="mailto:geoffreymina@gmail.com" target="_blank">geoffreymina@gmail.com</a>>
wrote:</p>
<p>This problem has been solved many times. The absolute
most bomb-proof<br>
MySQL failover solution involves a combination of DRBD and Linux HA<br>
(Heart Beat). The replication model has too many issues IMO.</p>
<div>
<div>
<p><br>
<br>
<br>
<br>
On Sun, Nov 23, 2008 at 9:10 AM, Uwe Kastens <<a href="mailto:kiste@kiste.org" target="_blank">kiste@kiste.org</a>> wrote:<br>
> Hi Krunal,<br>
>> * I am having 2 MySql servers. Lets say <a href="http://192.168.1.5" target="_blank">192.168.1.5</a><br>
>> <<a href="http://192.168.1.5" target="_blank">http://192.168.1.5</a>>
& <a href="http://192.168.1.6" target="_blank">192.168.1.6</a> <<a href="http://192.168.1.6" target="_blank">http://192.168.1.6</a>><br>
>> * Opensips is at <a href="http://192.168.1.4" target="_blank">192.168.1.4</a> <<a href="http://192.168.1.4" target="_blank">http://192.168.1.4</a>>.<br>
>> * I would like to use <a href="http://192.168.1.6" target="_blank">192.168.1.6</a> <<a href="http://192.168.1.6" target="_blank">http://192.168.1.6</a>>
mysql server<br>
>> for failover.<br>
>> * I mean to say if <a href="http://192.168.1.5" target="_blank">192.168.1.5</a> <<a href="http://192.168.1.5" target="_blank">http://192.168.1.5</a>>
goes down then<br>
>> opensips should start to use <a href="http://192.168.1.6" target="_blank">192.168.1.6</a> <<a href="http://192.168.1.6" target="_blank">http://192.168.1.6</a>><br>
>> mysql server.<br>
>><br>
><br>
> I am just on my way to implement the same. At the moment I am planing a<br>
> kind of Mysql Master - Master together with one VIP for<br>
> Mysql-opensips-communication. So for your example you will have to<br>
> mysql-servers. opensips is connection to lets say to <a href="http://192.168.1.4" target="_blank">192.168.1.4</a> which<br>
> points on one of your mysql-servers. You will need active-active for<br>
> mysql since opensips will write some information in the database as well.<br>
><br>
><br>
> I am working with mysql-5 and heartbeat-2 in mode 1. Its nearly working.<br>
><br>
> BR<br>
><br>
> Kiste<br>
><br>
> --<br>
><br>
> kiste lat: 54.322684, lon: 10.13586<br>
></p>
</div>
</div>
<div>
<div>
<p>> _______________________________________________<br>
> Users mailing list<br>
> <a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a><br>
> <a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
><br>
<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a></p>
</div>
</div>
</div>
<p> </p>
</div>
</div>
<p style="margin-bottom:12.0pt"><br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a></p>
</div>
<p> </p>
</div></div></div>
</div>
<br>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
<br></blockquote></div><br></div>