mysql主從復制延遲解決，mysql5.6主從不報錯_mysql5.6.26主從復制報錯1050

一天老大要求做mysql5.6的數據庫的主從復制，，但是報錯了，提示1050數據表已存在錯誤：

Last_SQL_Errno: 1050

Last_SQL_Error: Error 'Table 'authWeibo' already exists' on query. Default database: 'novel'. Query: 'CREATE TABLE `authWeibo` (

`userId` int(11) unsigned NOT NULL AUTO_INCREMENT,

`unionId` varchar(100) DEFAULT NULL,

mysql主從復制延遲解決？PRIMARY KEY (`userId`)

) ENGINE=InnoDB ?DEFAULT CHARSET=utf8mb4'

[root@localhost log]# tailf error.log

2017-08-10 23:19:30 10076 [Note] Slave I/O thread: connected to master 'novelrep@192.168.10.98:3306',replication started in log 'FIRST' at position 4

2017-08-10 23:19:30 10076 [Warning] Slave SQL: If a crash happens this configuration does not guarantee that the relay log info will be consistent, Error_code: 0

2017-08-10 23:19:30 10076 [Note] Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log './localhost-relay-bin.000001' position: 4

mysql主從切換步驟，2017-08-10 23:49:50 10076 [ERROR] Slave SQL: Error 'Table 'authWeibo' already exists' on query. Default database: 'novel'. Query: 'CREATE TABLE `authWeibo` (

`userId` int(11) unsigned NOT NULL AUTO_INCREMENT,

`unionId` varchar(100) DEFAULT NULL,

PRIMARY KEY (`userId`)

) ENGINE=InnoDB ?DEFAULT CHARSET=utf8mb4', Error_code: 1050

2017-08-10 23:49:50 10076 [Warning] Slave: Table 'authWeibo' already exists Error_code: 1050

mysql主從和集群的區別、2017-08-10 23:49:50 10076 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'mysql-bin.000073' position 1025057034

解決辦法：

slave從庫上停止從庫復制線程，重置從庫復制賬戶信息和同步失敗的binlog文件以及同步失敗的binglog位置點：

stop slave;

reset slave;

CHANGE MASTER TO ?MASTER_HOST='192.168.10.98',MASTER_PORT=3306,MASTER_USER='novelrep',MASTER_PASSWORD='JuwoSdk21TbUser',master_log_file='mysql-bin.000073

MySQL主從復制原理，',master_log_pos=1025057034;start slave;show slave status\G

到此同步成功

本文轉自 wjw555 51CTO博客，原文鏈接:http://blog.51cto.com/wujianwei/1955660