[Freeswitch-users] Using mysql cluster as core db

[Ash]

Hi Gary,

I used to use mysql cluster on my tables for the freeswitch database.  When I set it up I started freeswitch which created the tables as MyISAM, then I run an ALTER TABLE X type=ndbcluster on each table this worked for me.  I thought you could tune the NDB config file to allow more elements.  Did you try raising your Data Size and Index Sizes?   There is a nab_size.pl script which can help you work things out I believe.

I actually ended up moving away from NDB for my FS database as I was suffering strange lock issues and lock errors, NDB seems very limited in the locking mechanism it does and in some case I found the sip_registrations table was actually locked which caused an outage for my clients.  I moved to a Innodb Active/Active replication scenario, in doing so I found that the locking issues went away and in fact the SQL queries got faster thanks to indexing.  With the InnoDB setup you can still achieve high availability by using Active/Active replication and a virtual address that is monitored using heartbeat.

Entirely up to you but after the experience I had I would strongly advise against NDB Cluster for your FS Core, initially it was great but as my volume increased I started seeing ODBC lock timeout messages from Freeswitch, as soon as I change the tables to Innodb the lock error messages disappeared.

Cheers,

Ash.


On 22/03/2012, at 6:05 AM, GCHEN00 wrote:

> mysql cluster 7.2.4
> and newest FS
>  
> I am trying to use ODBC to connect mysql cluster database.
> When FS start, it has ERRORs to create the tables channel and interfaces, So I tried to manually create these two tables with schema from non-cluster mysql database.
> With engine=NDBCLUSTER for the tables, I got this error: "The maximum row size for the used table type, not counting BLOBs, is 14000. You have to change some columns to TEXT or BLOBs"
>  
> I can use engine=InnoDB but not NDBCLUSTER.
>  
> So I changed fields 'presence_id' and 'presence_data' in channel table from size 4096 to 512 and field 'description' in interfaces table from 4096 to 1024. And it worked.
>  
> I am wordering will these table changes cause any problem down the road.
>  
> Any other suggestion to solve this problem?
>  
> Gary
>  
>  
> _________________________________________________________________________
> Professional FreeSWITCH Consulting Services:
> consulting at freeswitch.org
> http://www.freeswitchsolutions.com
> 
> 
> 
> 
> Official FreeSWITCH Sites
> http://www.freeswitch.org
> http://wiki.freeswitch.org
> http://www.cluecon.com
> 
> FreeSWITCH-users mailing list
> FreeSWITCH-users at lists.freeswitch.org
> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
> http://www.freeswitch.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20120322/727fa2a9/attachment.html