INNODB TABLES on vicidial
Moderators: gerski, enjay, williamconley, Op3r, Staydog, gardo, mflorell, MJCoate, mcargile, Kumba, Michael_N
3 posts
• Page 1 of 1
INNODB TABLES on vicidial
by bulcrack » Mon Mar 19, 2007 5:59 am
Anyone using innodb tables on vicidial here?
- bulcrack
- Posts: 24
- Joined: Sat Jun 10, 2006 11:01 am
- Location: Philippines
by mflorell » Sun Feb 08, 2009 10:57 pm
Just wanted to update this thread and several others with a recent InnoDB experience of ours.
We recently signed a new client that had 48 outbound seats of VICIDIAL on two servers and had MySQL with InnoDB tables set up on it. The client was having random pausing issues that were not caused by any of the normal problems of server load, workstation issues or networking issues. The loadavg on the database server was actually very low. After adding hundreds of lines of MySQL debugging to the vicidial.php agent screen and the other related agent scripts we discovered that the problem was with InnoDB deadlocks, which can occur on InnoDB systems even if you are not using transactions(which VICIDIAL does not). In spite of all of our efforts and even with a great deal of error checking and retry loops put into the code we could not colve the problem completely until we switched the database to MyISAM, then the problem never resurfaced.
Because of this experience we do not recommend using InnoDB as your MySQL storage engine, and if you are, please let us know if you run into any deadlock issues like we have found or if you were able to make it work more reliably than we could.
We recently signed a new client that had 48 outbound seats of VICIDIAL on two servers and had MySQL with InnoDB tables set up on it. The client was having random pausing issues that were not caused by any of the normal problems of server load, workstation issues or networking issues. The loadavg on the database server was actually very low. After adding hundreds of lines of MySQL debugging to the vicidial.php agent screen and the other related agent scripts we discovered that the problem was with InnoDB deadlocks, which can occur on InnoDB systems even if you are not using transactions(which VICIDIAL does not). In spite of all of our efforts and even with a great deal of error checking and retry loops put into the code we could not colve the problem completely until we switched the database to MyISAM, then the problem never resurfaced.
Because of this experience we do not recommend using InnoDB as your MySQL storage engine, and if you are, please let us know if you run into any deadlock issues like we have found or if you were able to make it work more reliably than we could.
- mflorell
- Site Admin
- Posts: 18339
- Joined: Wed Jun 07, 2006 2:45 pm
- Location: Florida
3 posts
• Page 1 of 1
Who is online
Users browsing this forum: Google [Bot] and 247 guests