Re: Lock wait timeout exceeded - MySQL 5.6.15-ndb-7.3.4
Quote
... multiple threads are accessing the same row of a table; one thread is trying to update the record and the other thread is trying to delete the same row entry. Both the connections are locking the same row (I am using ndbcluster, and it does row-level locking) ...
If users are trying to simultaneously update & delete the same row, the design may need tweaking.
If such simultaneities actually make sense in the app context, you could code graceful contention-handling options, eg invite the updating the user to relinquish control for the delete request, and inform the delete requester if the first request was declined.
Or implement a transaction semaphore table to enforce one-tx-at-a-time-per-row and provide graceful wait messages.
Subject
Views
Written By
Posted
5124
December 10, 2014 11:51AM
Re: Lock wait timeout exceeded - MySQL 5.6.15-ndb-7.3.4
1779
December 10, 2014 12:45PM
1546
December 10, 2014 01:15PM
1455
December 10, 2014 02:53PM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.