[Vtigercrm-developers] Deadlock found when trying to get lock
lajeeshk at gmail.com
Mon Jul 15 15:40:53 GMT 2019
Also refere to this doc
Freelance developer / entrepreneur
On Mon, Jul 15, 2019 at 9:10 PM lajeesh k <lajeeshk at gmail.com> wrote:
> Hi Alan,
> The possible reason for this issue is In some places of vtiger it
> uses $this->db and in some some place $adb in the same transaction. This
> can cause lock
> Also If any transaction didn't completed successfully , I can cause lock
> for the other coming transactions
> you can refer this doc to find out the process causing lock and kill that
> use these queries
> show full processlist;
> SHOW ENGINE INNODB STATUS;
> Freelance developer / entrepreneur
> On Mon, Jul 15, 2019 at 8:29 PM nilay khatri <nilay.spartan at gmail.com>
>> We faced a similar issue, but no solution till now.
>> Customer moved to MariaDB and surprisingly it did not repeat.
>> On Mon, Jul 15, 2019 at 7:31 PM Alan Lord <alanslists at gmail.com> wrote:
>>> I have a customer with a very large vtiger system (> 500 users, millions
>>> of rows) and occasionally, after adding some debug code to try and find
>>> what the problem was, I managed to get the above error message after an
>>> INSERT operation from the PearDatabase object.
>>> The MySQL docs recommend coding for this by retrying the operation if a
>>> deadlock happens. I can probably do this but was wondering if anyone
>>> else has seen this before and if so how did they deal with it?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the vtigercrm-developers