[Vtigercrm-developers] I was seeing this quite often: [1205]Lock wait timeout exceeded

[Alan Lord]

This is kind of an FYI really. I'd seen it before.

This is on a dev server, am using a very recent branch from master on 
code.vtiger.com and I'm the only user and nothing much else is going on. 
I've seen this happen quite a few times during development and testing. 
In this particular case I just tried saving a record to trigger an Event 
Handler and I can make it happen pretty much every time I save this 
particular record... From the user's perspective the save process takes 
ages (several minutes) and eventually the screen reloads and the change 
to the record's data *wasn't* saved...

> Thu Jun 18 11:17:14 2020,932 [16878] DEBUG VT - Prepared sql query parameters : [7,0,1,,2020-06-18 11:17:14,5253]
> Thu Jun 18 11:18:05 2020,960 [16878] INFO VT - PearDatabase ->ADODB error  Query Failed:update vtiger_crmentity set smownerid=?, smgroupid=?,modifiedby=?,description=?, modifiedtime=? where crmid=?::->[1205]Lock wait timeout exceeded; try restarting transaction

> PHP 7.2.24-0ubuntu0.18.04.6 (cli) (built: May 26 2020 13:09:11) ( NTS )
> Copyright (c) 1997-2018 The PHP Group
> Zend Engine v3.2.0, Copyright (c) 1998-2018 Zend Technologies
>     with Zend OPcache v7.2.24-0ubuntu0.18.04.6, Copyright (c) 1999-2018, by Zend Technologies

> mysql  Ver 14.14 Distrib 5.7.30, for Linux (x86_64) using  EditLine wrapper
> Copyright (c) 2000, 2020, Oracle and/or its affiliates. All rights reserved.

The dev system I am working on is a migrated vtiger 5.4.0 system...

There were over 200 tables (mostly the _seq but a few others) which were 
still set to MyISAM.

I converted all of them to InnoDB and now the problem seems to have gone 
away.

Hope this helps someone else.

Al