If you cannot restart mysql at this time, run this: SET GLOBAL innodb_lock_wait_timeout = 120 ![]() You can set it to higher value in /etc/my.cnf permanently with this line Īnd restart mysql. Purge done for trx's n:o show variables like 'innodb_lock_wait_timeout' MySQL thread id 3686635, query id 124164167 10.64.89.145 viget updatingĭELETE FROM file WHERE file_id in ('6dbafa39-7f00-0001-51f2-412a450be5cc' )įoreign key constraint fails for table `backoffice`.`attachment`:ĬONSTRAINT `attachment_ibfk_2` FOREIGN KEY (`file_id`) REFERENCES `file` (`file_id`) TRANSACTION 0 606162814, ACTIVE 0 sec, process no 29956, OS thread id 1223895360 updating or deleting, thread declared inside InnoDB 499ġ4 lock struct(s), heap size 3024, 8 row lock(s), undo log entries 1 ![]() OS WAIT ARRAY INFO: reservation count 9014315, signal count 7805377 Per second averages calculated from the last 4 seconds Here is a sample from one of my clients: mysql> show engine innodb status\G You get all kinds of additional Locking and Mutex Information. You should be able to see the affected table(s) Since you know the query, all the tables being accessed are candidates for being the culprit.įrom there, you should be able to run SHOW ENGINE INNODB STATUS\G ![]() It is evident by the statement that the query was attempting to change at least one row in one or more InnoDB tables. What gives this away is the word transaction.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |