收到報(bào)警，mysql的從數(shù)據(jù)庫在同步的過程出現(xiàn)問題，已停止同步。

ERROR] Slave SQL: ?Error ?"Lock wait timeout exceeded; try restarting transaction" on query. Default database: "yang". Query: "UPDATE workitem SET status = state, modify_time=1329640301 where workitem_id = 800", Error_cod

Slave sql not running: result is No|slave_sql_running=0

登錄數(shù)據(jù)庫查看！

root@127.0.0.1 : yang 16:48:34> show slave status \G;

*************************** 1. row ***************************

Slave_IO_State: Waiting for master to send event

Master_Host: 10.249.119.52

Master_User: replicator

Master_Port: 3306

Connect_Retry: 60

Master_Log_File: mysql-bin.001156

Read_Master_Log_Pos: 49021182

Relay_Log_File: slave-relay.118531

Relay_Log_Pos: 1342

Relay_Master_Log_File: mysql-bin.001156

Slave_IO_Running: Yes

Slave_SQL_Running: No

........

Last_Errno: 1205

Last_Error: Error 'Lock wait timeout exceeded; try restarting transaction' on query. Default database: 'yang'. Query: 'UPDATE workitem SET status = state, modify_time=1329640301 where workitem_id = 800'

Skip_Counter: 0

Exec_Master_Log_Pos: 47702497

Relay_Log_Space: 1319098

Until_Condition: None

Until_Log_File:

Until_Log_Pos: 0

Master_SSL_Allowed: No

...........

Seconds_Behind_Master: NULL

Master_SSL_Verify_Server_Cert: No

Last_IO_Errno: 0

Last_IO_Error:

Last_SQL_Errno: 1205

Last_SQL_Error: Error 'Lock wait timeout exceeded; try restarting transaction' on query. Default database: 'yang'. Query: 'UPDATE work SET status = state, modify_time=1329640301 where work_id = 800'

1 row in set (0.00 sec)

從庫由于Error 'Lock wait timeout exceeded; try restarting transaction' on query. Default database: 'yang'. Query: 'UPDATE work SET status = state, modify_time=1329640301 where work_id = 800'； 鎖等待超時導(dǎo)致事務(wù)失敗，多次重試不成功。Slave_SQL_進(jìn)程中斷！

解決辦法一:

1.首先停掉Slave服務(wù):

mysql>slave stop;

2.到主服務(wù)器上查看主機(jī)狀態(tài),

mysql> show master status;

+------------------+-----------+--------------+------------------+

| File ? ? ? ? ? ? | Position ?| Binlog_Do_DB | Binlog_Ignore_DB |

+------------------+-----------+--------------+------------------+

| mysql-bin.001156 | 48291554 ?| ? ? ? ? ? ? ?| ? ? ? ? ? ? ? ? ?|

+------------------+-----------+--------------+------------------+

1 row in set (0.00 sec)

記錄File和Position對應(yīng)的值 mysql-bin.001156,48291554

3 到slave服務(wù)器上執(zhí)行手動同步:

mysql> change master to

> master_host='master_ip',

> master_user='user',

> master_password='pwd',

> master_port=3306,

> master_log_file='mysql-bin.001156',

> master_log_pos=48291554;

1 row in set (0.00 sec)

mysql> slave start;

1 row in set (0.00 sec)

再次查看slave狀態(tài)發(fā)現(xiàn):

Slave_IO_Running: Yes

Slave_SQL_Running: Yes

...

Seconds_Behind_Master: 0

注:這種辦法可能會導(dǎo)致從服務(wù)器上的數(shù)據(jù)不完整,如從服務(wù)器一直出錯,但主服務(wù)器日志文件一直在增加,過好長時間,再直接從主服務(wù)器上取日志位置,可能會造成錯誤期間的數(shù)據(jù)無法更新到從服務(wù)器中.這里建議采用下面的這種辦法(將錯誤語句直接跳過).

解決辦法二:

mysql> slave stop;

mysql> set GLOBAL SQL_SLAVE_SKIP_COUNTER=1;

mysql> slave start;

set GLOBAL SQL_SLAVE_SKIP_COUNTER=N,用來跳過備機(jī)的一條或N條出錯的復(fù)制語句。然后重新start slave即可。

由于我們的是雙master 架構(gòu)，所以為了避免重復(fù)執(zhí)行變更的語句，實(shí)際操作：

root@127.0.0.1 : (none) 16:56:00> SET SQL_LOG_bin=0;

Query OK, 0 rows affected (0.00 sec)

root@127.0.0.1 : (none) 16:56:06> use yang;

Database changed

執(zhí)行導(dǎo)致錯誤的語句

root@127.0.0.1 : yang 16:56:10> UPDATE workitem SET status = state, modify_time=1329640301 where workitem_id = 800;

Query OK, 1 row affected (0.00 sec)

Rows matched: 1 ?Changed: 1 ?Warnings: 0

root@127.0.0.1 : yang 16:56:45>stop slave;

Query OK, 0 rows affected (0.00 sec)

root@127.0.0.1 : yang 16:56:46>set GLOBAL SQL_SLAVE_SKIP_COUNTER=1;

Query OK, 0 rows affected (0.00 sec)

root@127.0.0.1 : yang 16:56:46>start slave;

Query OK, 0 rows affected (0.00 sec)

最終確認(rèn)結(jié)果

root@127.0.0.1 : (none) 16:59:40> show slave status \G;

*************************** 1. row ***************************

Slave_IO_State: Waiting for master to send event

Master_Host: 10.249.119.52

Master_User: replicator

Master_Port: 3306

Connect_Retry: 60

Master_Log_File: mysql-bin.001156

Read_Master_Log_Pos: 49846932

Relay_Log_File: slave-relay.118532

Relay_Log_Pos: 235831

Relay_Master_Log_File: mysql-bin.001156

Slave_IO_Running: Yes

Slave_SQL_Running: Yes

..........

Last_Errno: 0

Last_Error:

Skip_Counter: 0

Exec_Master_Log_Pos: 49846932

Relay_Log_Space: 2144848

Until_Condition: None

Until_Log_File:

Until_Log_Pos: 0

Master_SSL_Allowed: No

Master_SSL_CA_File:

Master_SSL_CA_Path:

Master_SSL_Cert:

Master_SSL_Cipher:

Master_SSL_Key:

Seconds_Behind_Master: 0

Master_SSL_Verify_Server_Cert: No

Last_IO_Errno: 0

Last_IO_Error:

Last_SQL_Errno: 0

Last_SQL_Error:

1 row in set (0.00 sec)

至此問題解決~！

總結(jié)

以上是生活随笔為你收集整理的mysql sql running no_【MySql】复制出现Slave_SQL_Running: No 错误解决的全部內(nèi)容，希望文章能夠幫你解決所遇到的問題。

如果覺得生活随笔網(wǎng)站內(nèi)容還不錯，歡迎將生活随笔推薦給好友。