1

2

3

4

5

[2017-02-10 13:12:06.678] [INFO] mysqlLog - update tbl_playerdata_error: { [Error: ER_LOCK_DEADLOCK: Deadlock found when trying to get lock; try restarting transaction]

?code: 'ER_LOCK_DEADLOCK',

?errno: 1213,

?sqlState: '40001',

?index: 0 }

1

2

3

Message: Deadlock found when trying to get lock; try restarting transaction

?

InnoDB reports this error when a transaction encounters a deadlock and is automatically rolled back so that your application can take corrective action. To recover from this error, run all the operations in this transaction again. A deadlock occurs when requests for locks arrive in inconsistent order between transactions. The transaction that was rolled back released all its locks, and the other transaction can now get all the locks it requested. Thus, when you re-run the transaction that was rolled back, it might have to wait for other transactions to complete, but typically the deadlock does not recur. If you encounter frequent deadlocks, make the sequence of locking operations (LOCK TABLES, SELECT ... FOR UPDATE, and so on) consistent between the different transactions or applications that experience the issue. See Section 14.8.5, “Deadlocks in InnoDB” for details.

1

To recover from this error, run all the operations in this transaction again<br><br>If you encounter frequent deadlocks, make the sequence of locking operations (<code class="literal">LOCK TABLES</code>, <code class="literal">SELECT ... FOR UPDATE</code>, and so on) <br>consistent between the different transactions or applications that experience the issue

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

One easy trick that can help with most deadlocks is sorting the operations in a specific order.

?

You get a deadlock when two transactions are trying to lock two locks at <a href="https://www.xiaojishu.com/tags/oppo.html" target="_blank" class="infotextkey">OPPO</a>site orders, ie:

?

connection 1: locks key(1), locks key(2);

connection 2: locks key(2), locks key(1);

If both run at the same time, connection 1 will lock key(1), connection 2 will lock key(2) and each connection will wait for the other to release the key -> deadlock.

?

Now, if you changed your queries such that the connections would lock the keys at the same order, ie:

?

connection 1: locks key(1), locks key(2);

connection 2: locks key(1), locks key(2);

it will be impossible to get a deadlock.

?

So this is what I suggest:

?

Make sure you have no other queries that lock access more than one key at a time except for the delete statement. if you do (and I suspect you do), order their WHERE in (k1,k2,..kn) in ascending order.

Fix your delete statement to work in ascending order:

Change

?

DELETE FROM onlineusers WHERE datetime <= now() - INTERVAL 900 SECOND

To

?

DELETE FROM onlineusers WHERE id IN (SELECT id FROM onlineusers

?WHERE datetime <= now() - INTERVAL 900 SECOND order by id) u;

Another thing to keep in mind is that mysql documentation suggest that in case of a deadlock the client should retry automatically. you can add this logic to your client code. (Say, 3 retries on this particular error before giving up).