【发布时间】:2016-09-13 05:18:01
【问题描述】:
在我的rails项目中,我使用sidekiq处理耗时任务,但在sidekiq中记录错误:
ActiveRecord::StatementInvalid: Mysql2::Error: Lock wait timeout exceeded; try restarting transaction: UPDATE `marker_layers` SET `show_fields` = 'title,desc', `sort_col` = 'title,desc', `updated_at` = '2016-05-17 07:36:02' WHERE `marker_layers`.`id` = 16021210
Processor: iZ23edse84Z:29310
# Options here can still be overridden by cmd line args.
# setsid sidekiq -d -C config/sidekiq.yml -e production
---
:concurrency: 5
:pidfile: tmp/pids/sidekiq.pid
:logfile: log/sidekiq.log
staging:
:concurrency: 10
production:
:concurrency: 40
:queues:
- ['critical', 3]
- ['default', 2]
- ['low', 1]
database.yml
production:
adapter: mysql2
encoding: utf8mb4
collation: utf8mb4_bin
reconnect: false
database: database_name
pool: 48
username: password
password: password
host: locahost
【问题讨论】:
-
很可能有多个工作人员尝试更新同一数据库行,并在等待访问时超时。根据您的信息,我们无法提供更多信息。您可能应该重新检查您的代码以了解竞争条件并查看死锁来自何处......
-
您可能会发现stackoverflow.com/questions/6000336/… 有帮助
-
您可能还想了解
innodb_lock_wait_timeout和innodb_deadlock_detect变量
标签: mysql ruby-on-rails activerecord sidekiq