-------------------quote begin------------------------ 3. If you decide that you can skip the next statement from the master, issue the following statements: mysql> SET GLOBAL SQL_SLAVE_SKIP_COUNTER = n; mysql> START SLAVE; The value of n should be 1 if the next statement from the master does not use AUTO_INCREMENT or LAST_INSERT_ID(). Otherwise, the value should be 2. The reason for using a value of 2 for statements that use AUTO_INCREMENT or LAST_INSERT_ID() is that they take two events in the binary log of the master.
-------------------quote end------------------------
MySQL文档中的意思是当master传到slave的语句中要用到auto_increment,或者last_insert_id()时,需要skip两个event. 但实际情况并非如此
测试过程如下: 172.16.161.26 为master 172.16.161.15 为slave 同步c2cdb，初始状态ok
1. 在master上创建测试表
?
| 12 | mysql> create table tmp_test_0208(id int not null auto_increment,name varchar(30),primary key(id)) engine=innodb;Query OK, 0 rows affected (0.20 sec) |
2, 在salve上insert 3条记录
?
| 12345678910111213 | mysql> insert into tmp_test_0208 values(1,'a'),(2,'b'),(3,'c');Query OK, 3 rows affected (0.00 sec)Records: 3 Duplicates: 0 Warnings: 0 mysql> select * from tmp_test_0208;+----+------+| id | name |+----+------+| 1 | a || 2 | b || 3 | c |+----+------+3 rows in set (0.00 sec) |
3, 在master上insert 3条记录
?
| 12345678910111213 | mysql> insert into tmp_test_0208(name) values('a'),('b'),('c');Query OK, 3 rows affected (0.02 sec)Records: 3 Duplicates: 0 Warnings: 0 mysql> select * from tmp_test_0208;+----+------+| id | name |+----+------+| 1 | a || 2 | b || 3 | c |+----+------+3 rows in set (0.00 sec) |
4, slave 的sql thread 中止
?
| 1234 | /usr/local/mysql/bin/mysql -uroot -pxxx c2cdb -s -e "show slave status\G" |egrep "Slave_IO_Running|Slave_SQL_Running"Slave_IO_Running: YesSlave_SQL_Running: No |
5, skip next statemate后start slave正常
?
| 12345678910 | mysql> SET GLOBAL SQL_SLAVE_SKIP_COUNTER = 1 ;Query OK, 0 rows affected (0.00 sec) mysql> slave start;Query OK, 0 rows affected (0.00 sec) /usr/local/mysql/bin/mysql -uroot -pxxx c2cdb -s -e "show slave status\G" |egrep "Slave_IO_Running|Slave_SQL_Running"Slave_IO_Running: YesSlave_SQL_Running: Yes |
slave端errlog如下： 070208 16:07:59[ERROR] Slave: Error 'Duplicate entry '1' for key 1' on query. Default database: 'c2cdb'. Query: 'insert into tmp_te st_0208(name) values('a'),('b'),('c')', Error_code: 1062
070208 16:07:59 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db_auction1-bin.000203' position 14215101
070208 16:09:59 [Note] Slave SQL thread initialized, starting replication in log 'db_auction1-bin.000203' at position 14215101, rela y log './db_auction1_b-relay-bin.000457' position: 200682931
master羰binlog中相应的记录如下：
# at 14215101 #070208 16:08:00 server id 1 log_pos 14215101 Intvar SET INSERT_ID=1; # at 14215129 #070208 16:08:00 server id 1 log_pos 14215129 Query thread_id=2744782 exec_time=0 error_code=0 SET TIMESTAMP=1170922080; insert into tmp_test_0208(name) values('a'),('b'),('c');
总结：使用SET GLOBAL SQL_SLAVE_SKIP_COUNTER 命令跳过失败的SQL
共同学习，写下你的评论
评论加载中...
作者其他优质文章
