[Freeswitch-dev] Accidental deadlocks

[mcom]

Hello,


I've got few freeswitch servers sharing same data base placed on Percona
Galera cluster.
Accidentally I observe deadlocks - example below:


2015-01-13T21:51:23.531909+00:00 fs1dev freeswitch[3357]: 2015-01-13
21:51:22.414677 [ERR] switch_core_sqldb.c:581 ODBC SQL ERR [STATE: HY000
CODE 1213 ERROR: [unixODBC][MySQL][ODBC 5.1
Driver][mysqld-5.6.15-63.0]Deadlock found when trying to get lock; try
restarting transaction#012]#012update sip_authentication set
expires='1421185972',last_nc=15 where
nonce='6544a9e0-9b6d-11e4-9010-a17af9ccfef5

I've found that in case of Percona Galera cluster deadlocks are
something that could happen:

 http://www.percona.com/blog/2012/08/17/percona-xtradb-cluster-multi-node-writing-and-unexpected-deadlocks/


Now I have option to set automatic retry on Percona Galera cluster
(which is a bit dangerous since freeswitch won't be aware
of that there was some problem with transaction) but it's not a best
choice. I wonder if freeswich do retry after such error? - that
would be the best option. 

-- 
Pozdrawiam
Wojciech Matys