[asterisk-dev] Realtime Failover - Multiple DSNs

[Stefan Schmidt]

Hi Stuart,

I suggest to take a look at mysql mmm cluster (mysql-mmm.org) this is a
cluster setup with roles (and unique ips for each role) which handle
over the roles to other servers if one is unreachable. it has many
advantages to the normal mysql cluster and there are also debian
packages (if you use debian ;)

i have now a project to build a cluster with this and it has many
advantages against the mysql-cluster (NDB) and you didnt need dynamic dns.

mysql-proxy is also a nice solution but it depends on your needs if it
is really the best way.

best regards

Stefan Schmidt

Am 27.06.11 11:58, schrieb Stuart Elvish:
> Hi Stefan,
> 
> Thanks for the suggestion.
> 
> I had seen mysql-proxy when I was searching for a solution. Have you
> used it? Does it work really well?
> 
> Kind Regards
> Stuart Elvish
> 
> On 27 June 2011 16:42,  <arcopix at erihon.com> wrote:
>> Hello,
>>
>> Have you tried using mysql-proxy? It can be a temporary solution for
>> your case. You can install the mysql-proxy on the local machine and it i
>> will reroute the queries to different mySQL nodes.
>>
>> Regards,
>> Stefan Lekov
>>
>> On Mon, 27 Jun 2011 16:26:50 +0700, Stuart Elvish
>> <stuart.elvish at gmail.com> wrote:
>>> Hi All,
>>>
>>> This was originally posted on the asterisk-users list but I didn't
>>> receive any responses. Here's hoping that someone on the dev list can
>>> point me in the right direction.
>>>
>>> I currently have 3 servers setup to provide a small MySQL cluster. I
>>> can easily run custom database queries via func_odbc and res_odbc with
>>> failover DSN's (up to five) but I can't seem to add any failover DSN's
>>> into the realtime configuration file (extconfig.conf). Has anyone been
>>> able to configure either the standard ODBC driver or Asterisk to use a
>>> failover DSN for realtime system configuration?
>>>
>>> Currently my extconfig.conf has a setup something similar to this:
>>> sippeers => odbc,mysql-asterisk,sipendpoints but being
>>>
>>> Currently we use a floating IP between the MySQL data nodes (as we
>>> query each directly) but Asterisk, MySQL or ODBC (I am not sure which)
>>> has problems when one of the nodes goes offline and Asterisk stops
>>> being able to query the database successfully. I see Asterisk passing
>>> queries to the MySQL server (shows up in the logs) but the queries
>>> aren't successful (they aren't updating the SIP registration
>>> information) and Asterisk is throwing up errors on the CLI. Being able
>>> to define multiple DSN's I presume would fix this problem.
>>>
>>> Any advice would be greatly appreciated.
>>>
>>> Kind Regards
>>> Stuart Elvish
>>>
>>> --
>>> _____________________________________________________________________
>>> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>>>
>>> asterisk-dev mailing list
>>> To UNSUBSCRIBE or update options visit:
>>>    http://lists.digium.com/mailman/listinfo/asterisk-dev
>>
>>
>> --
>> _____________________________________________________________________
>> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>>
>> asterisk-dev mailing list
>> To UNSUBSCRIBE or update options visit:
>>   http://lists.digium.com/mailman/listinfo/asterisk-dev
>>
> 
> --
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
> 
> asterisk-dev mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-dev


-- 
Für weitere Fragen stehen wir gerne unter voip at sil.at oder
059944 - 2440 zur Verfügung.

Mit freundlichen Grüssen
-- 
Stefan Schmidt
Teamleiter VOIP // voip at sil.at // Tel 059944-2440//
-------------------------------------------------
SILVER SERVER GmbH // Lorenz-Mandl-Gasse 33/1 //
A-1160 Wien // Fax 059944-9000 // www.sil.at  //
-------------------------------------------------