ERROR 1205 (HY000): Lock wait timeout exceeded; try restarting transaction
前言：朋友咨詢我說執(zhí)行簡(jiǎn)單的update語(yǔ)句失效，癥狀如下：
mysql>?update?order_info??set?province_id=15??,city_id=?1667??where?order_from=10?and?order_out_sn='1407261241xxxx';
ERROR?1205?(HY000):?Lock?wait?timeout?exceeded;?try?restarting?transaction
mysql>?
QQ遠(yuǎn)程過去，開始check
1，查看數(shù)據(jù)庫(kù)的隔離級(jí)別：
mysql>?select?@@tx_isolation;
+-----------------+
|?@@tx_isolation??|
+-----------------+
|?REPEATABLE-READ?|
+-----------------+
1?row?in?set?(0.00?sec)
mysql>?
?
2，去查看先當(dāng)前庫(kù)的線程情況：
mysql> show full processlist;
+----------+-----------------+-------------------+-----------------+-------------+---------+-------------------------+-----------------------+
| Id?????? | User??????????? | Host????????????? | db????????????? | Command???? | Time??? | State?????????????????? | Info????????????????? |
+----------+-----------------+-------------------+-----------------+-------------+---------+-------------------------+-----------------------+
|??????? 1 | event_scheduler | localhost???????? | NULL??????????? | Daemon????? | 9635385 | Waiting on empty queue? | NULL????????????????? |
|??9930577?| business_web??? | 192.168.1.21:45503 | business_db???? | Sleep?????? |???? 153 |???????????????????????? | NULL????????????????? |
|? 9945825 | business_web??? | 192.168.1.25:49518 | business_db???? | Sleep?????? |????? 43 |???????????????????????? | NULL????????????????? |
|? 9946322 | business_web??? | 192.168.1.23:44721 | business_db???? | Sleep?????? |???? 153 |???????????????????????? | NULL????????????????? |
|? 9960167 | business_web??? | 192.168.3.28:2409? | business_db???? | Sleep?????? |????? 93 |???????????????????????? | NULL????????????????? |
|? 9964484 | business_web??? | 192.168.1.21:24280 | business_db???? | Sleep?????? |?????? 7 |???????????????????????? | NULL????????????????? |
|? 9972499 | business_web?? ?| 192.168.3.28:35752 | business_db???? | Sleep?????? |????? 13 |???????????????????????? | NULL????????????????? |
| 10000117 | business_web??? | 192.168.3.28:9149? | business_db???? | Sleep?????? |?????? 6 |???????????????????????? | NULL????????????????? |
| 10002523 | business_web??? | 192.168.3.29:42872 | business_db???? | Sleep?????? |?????? 6 |???????????????????????? | NULL????????????????? |
| 10007545 | business_web??? | 192.168.1.21:51379 | business_db???? | Sleep?????? |???? 155 |?????????????????? ??????| NULL????????????????? |
......
+----------+-----------------+-------------------+-----------------+-------------+---------+-------------------------+-----------------------+
?
沒有看到正在執(zhí)行的慢SQL記錄線程，再去查看innodb的事務(wù)表INNODB_TRX，看下里面是否有正在鎖定的事務(wù)線程，看看ID是否在show full processlist里面的sleep線程中，如果是，就證明這個(gè)sleep的線程事務(wù)一直沒有commit或者rollback而是卡住了，我們需要手動(dòng)kill掉。
?
mysql> SELECT * FROM information_schema.INNODB_TRX\G;
*************************** 1. row ***************************
??????????????????? trx_id: 20866
???????????????? trx_state: LOCK WAIT
?????????????? trx_started: 2014-07-31 10:42:35
???? trx_requested_lock_id: 20866:617:3:3
????????? trx_wait_started: 2014-07-30 10:42:35
??????????????? trx_weight: 2
?????? trx_mysql_thread_id:?9930577
???????????????? trx_query: delete from dltask where id=1
?????? trx_operation_state: starting index read
???????? trx_tables_in_use: 1
???????? trx_tables_locked: 1
????????? trx_lock_structs: 2
???? trx_lock_memory_bytes: 376
?????????? trx_rows_locked: 1
???????? trx_rows_modified: 0
?? trx_concurrency_tickets: 0
?????? trx_isolation_level: READ COMMITTED
???????? trx_unique_checks: 1
??? trx_foreign_key_checks: 1
trx_last_foreign_key_error: NULL
?trx_adaptive_hash_latched: 0
?trx_adaptive_hash_timeout: 10000
????????? trx_is_read_only: 0
trx_autocommit_non_locking: 0
?
3，看到有這條9930577的sql，kill掉，執(zhí)行kill 9930577;
mysql> kill 9930577;
Query OK, 0 rows affected (0.00 sec)
?
mysql>
?
然后再去查詢INNODB_TRX表，就沒有阻塞的事務(wù)sleep線程存在了，如下所示：
mysql> SELECT * FROM INNODB_TRX\G;
Empty set (0.00 sec)
?
ERROR:
No query specified
?
mysql>
再去執(zhí)行update語(yǔ)句，就能正常執(zhí)行了，如下所示：
mysql> update order_info? set province_id=15? ,city_id= 1667? where order_from=10 and order_out_sn='1407261241xxxx';
Query OK, 1 row affected (0.00 sec)
Rows matched: 1? Changed: 1? Warnings: 0
?
mysql>
4，總結(jié)分析
表數(shù)據(jù)量也不大，按照普通的情況來(lái)說，簡(jiǎn)單的update應(yīng)該不會(huì)造成阻塞的，mysql都是autocommit，不會(huì)出現(xiàn)update卡住的情況，去查看下autocommit的值。
mysql> select @@autocommit;
+--------------+
| @@autocommit |
+--------------+
| ? ? ? ? ???0?|
+--------------+
1 row in set (0.00 sec)
mysql>
看到亮閃閃的0，這個(gè)設(shè)置導(dǎo)致原來(lái)的update語(yǔ)句如果沒有commit的話，你再重新執(zhí)行update語(yǔ)句，就會(huì)等待鎖定，當(dāng)?shù)却龝r(shí)間過長(zhǎng)的時(shí)候，就會(huì)報(bào)ERROR?1205?(HY000):?Lock?wait?timeout?exceeded;?try?restarting?transaction的錯(cuò)誤。
所以趕緊commit剛才執(zhí)行的update語(yǔ)句，之后 set global?autocommit=1;
來(lái)自：http://blog.itpub.net/26230597/viewspace-1242948/
總結(jié)
以上是生活随笔為你收集整理的ERROR 1205 (HY000): Lock wait timeout exceeded; try restarting transaction的全部?jī)?nèi)容，希望文章能夠幫你解決所遇到的問題。
- 上一篇： 使用Memcache缓存mysql数据库
- 下一篇： innobackupex中--slave