程序奔溃导致mysql事务未提交
> SHOW ENGINE INNODB STATUS;
RANSACTIONS
------------
Trx id counter 74862
Purge done for trx's n:o < 74862 undo n:o < 0 state: running but idle
History list length 2
LIST OF TRANSACTIONS FOR EACH SESSION:
---TRANSACTION 421544929007128, not started
0 lock struct(s), heap size 1128, 0 row lock(s)
---TRANSACTION 421544929006320, not started
0 lock struct(s), heap size 1128, 0 row lock(s)
---TRANSACTION 421544929002280, not started
0 lock struct(s), heap size 1128, 0 row lock(s)
---TRANSACTION 421544929000664, not started
0 lock struct(s), heap size 1128, 0 row lock(s)
---TRANSACTION 421544929005512, not started
0 lock struct(s), heap size 1128, 0 row lock(s)
---TRANSACTION 421544929001472, not started
0 lock struct(s), heap size 1128, 0 row lock(s)
---TRANSACTION 421544929004704, not started
0 lock struct(s), heap size 1128, 0 row lock(s)
---TRANSACTION 421544929003896, not started
0 lock struct(s), heap size 1128, 0 row lock(s)
---TRANSACTION 421544928999856, not started
0 lock struct(s), heap size 1128, 0 row lock(s)
---TRANSACTION 421544928999048, not started
0 lock struct(s), heap size 1128, 0 row lock(s)
---TRANSACTION 74858, ACTIVE 64 sec
2 lock struct(s), heap size 1128, 1 row lock(s)
MySQL thread id 46163, OS thread handle 140069038933568, query id 2915675
可以发现有一个事务活跃64s, 线程是46163
通过show processlist,找到对应的线程kill
本作品采用《CC 协议》,转载必须注明作者和本文链接
可以设置超时自动回滚
try catch rollback不好使吗?mysql.ini中设置innodb_lock_wait_timeout.