Question

更新表中用户的最后活动时，在MariaDB（10.1）中陷入僵局。

导致错误的查询是

UPDATE auth_sessions SET last_activity_time='2018-12-21 05:45:39 WHERE id= 481;

只要用户对应用程序执行任何操作，我们就会在过程内执行此查询。

以下是从show engine innodb status ;收到的状态

------------------------
LATEST DETECTED DEADLOCK
------------------------
2018-12-21 05:45:39 7fe5b8e6eb00
*** (1) TRANSACTION:
TRANSACTION 3742528, ACTIVE 0 sec starting index read
mysql tables in use 1, locked 1
LOCK WAIT 12 lock struct(s), heap size 2936, 81 row lock(s)
MySQL thread id 1941, OS thread handle 0x7fe5b5df4b00, query id 43106 localhost 127.0.0.1 root updating
UPDATE auth_sessions
                                                    SET last_activity_time= NAME_CONST('time_now',_latin1'2018-12-21 05:45:39' COLLATE 'latin1_swedish_ci')
                                                    WHERE id= NAME_CONST('temp_session_id',481)
*** (1) WAITING FOR THIS LOCK TO BE GRANTED:
RECORD LOCKS space id 470949 page no 6 n bits 160 index `PRIMARY` of table `xfusion_auth_engine`.`auth_sessions` trx table locks 5 total table locks 5  trx id 3742528 lock_mode X locks rec but not gap waiting lock hold time 0 wait time before grant 0 
*** (2) TRANSACTION:
TRANSACTION 3742527, ACTIVE 0 sec starting index read
mysql tables in use 1, locked 1
12 lock struct(s), heap size 2936, 81 row lock(s)
MySQL thread id 1943, OS thread handle 0x7fe5b8e6eb00, query id 43123 localhost 127.0.0.1 root updating
UPDATE auth_sessions
                                                    SET last_activity_time= NAME_CONST('time_now',_latin1'2018-12-21 05:45:39' COLLATE 'latin1_swedish_ci')
                                                    WHERE id= NAME_CONST('temp_session_id',481)
*** (2) HOLDS THE LOCK(S):
RECORD LOCKS space id 470949 page no 6 n bits 160 index `PRIMARY` of table `xfusion_auth_engine`.`auth_sessions` trx table locks 5 total table locks 5  trx id 3742527 lock mode S locks rec but not gap lock hold time 0 wait time before grant 0 
*** (2) WAITING FOR THIS LOCK TO BE GRANTED:
RECORD LOCKS space id 470949 page no 6 n bits 160 index `PRIMARY` of table `xfusion_auth_engine`.`auth_sessions` trx table locks 5 total table locks 5  trx id 3742527 lock_mode X locks rec but not gap waiting lock hold time 0 wait time before grant 0 
*** WE ROLL BACK TRANSACTION (2)
------------
TRANSACTIONS

表架构-身份验证会话

CREATE TABLE `auth_sessions` (
    `id` INT(11) NOT NULL AUTO_INCREMENT COMMENT 'Auto Increment ID',
    `user_id` VARCHAR(255) NULL DEFAULT NULL COMMENT 'User Email',
    `user_key` VARCHAR(255) NULL DEFAULT NULL COMMENT 'User Key',
    `application_key` VARCHAR(255) NULL DEFAULT NULL COMMENT 'Application Key',
    `created` DATETIME NULL DEFAULT NULL COMMENT 'Session Creation Time',
    `expires` DATETIME NULL DEFAULT NULL COMMENT 'Session Expiration Time',
    `is_logged_in` TINYINT(4) NULL DEFAULT NULL COMMENT 'Tells whether user is logged in or not ',
    `session_key` VARCHAR(255) NULL DEFAULT NULL COMMENT 'Session Key per user per application key',
    `last_activity_time` DATETIME NULL DEFAULT NULL COMMENT 'Last recorded time for any activity',
    `session_key_bin` BINARY(16) NULL DEFAULT NULL COMMENT 'Binary ID of Session Key',
    PRIMARY KEY (`id`),
    INDEX `ix_session_key_bin` (`session_key_bin`)
)

COLLATE='latin1_swedish_ci'
ENGINE=InnoDB

;

有解决此问题的线索或解决方案吗？

Answer 1

如果您有多语句交易（您没有）：

有时解决类似问题的方法

SELECT ... WHERE id= 481  FOR UPDATE;

在UPDATE之前，但在交易内部。

并非所有死锁都是可以避免的。最好准备处理死锁。可以通过以下方式正确处理这一特定问题：

计划A（首选）：重播UPDATE。

计划B（考虑到查询的目的，可能还可以）：忽略死锁。

计划C（我不知道它是否会工作；如果可行，应该消除这种死锁）：

UPDATE auth_sessions
    SET   last_activity_time = NOW()
    WHERE last_activity_time != NOW()
      AND id = 481;

该想法是避免在值已设置为所需时间的情况下尝试进行更新。

使用主键更新行时MariaDB死锁

1 个答案: