MySQL主从复制出错的解决方法

MySQL主从复制出错的解决方法

主从复制中若是出现错误可以通过几个方法来进行解决
1.如果主从复制时发生了主键冲突，从而阻止了主从复制，可以使用sql_slave_skip_counter这个变量来忽略错误将其排除
2.如果发生了较大的错误，可以考虑使用reset slave的方法重新配置从服务器来恢复错误

以下演示如何使用这两种方法解决错误，及相关操作的详细说明

reset slave的使用方法

环境准备搭建主从同步

主节点配置

1.修改配置文件

[[email protected] ~]# vim /etc/my.cnf
[mysqld]
log-bin=/data/bin/mysql-bin
binlog-format=row
server-id=1

2.创建二进制日志目录

[[email protected] ~]# mkdir /data/bin
[[email protected] ~]# chown -R mysql.mysql /data/bin

3.启动mysqld服务

[[email protected] ~]# systemctl start mariadb

4.查看主服务器日志位置

[[email protected] ~]# mysql -e "SHOW MASTER LOGS;"
+------------------+-----------+
| Log_name         | File_size |
+------------------+-----------+
| mysql-bin.000001 |     26753 |
| mysql-bin.000002 |    921736 |
| mysql-bin.000003 |       245 |
+------------------+-----------+

5.创建一个用来复制数据的账户

[[email protected] ~]# mysql -e "GRANT REPLICATION SLAVE ON *.* TO ‘repluser‘@‘192.168.73.%‘ IDENTIFIED BY ‘centos‘;"

从节点配置

1.修改配置文件

[[email protected] ~]# vim /etc/my.cnf
[mysqld]
read-only
server-id=2

2.启动服务

[[email protected] ~]# systemctl start mariadb

此处开始构建错误配置
以下所有CHANGE MASTER TO配置均为错误
3.配置CHANGE MASTER TO

MariaDB [(none)]> CHANGE MASTER TO
   ->   MASTER_HOST=‘master2.mycompany.com‘,
   ->   MASTER_USER=‘replication‘,
   ->   MASTER_PASSWORD=‘bigs3cret‘,
   ->   MASTER_PORT=3306,
   ->   MASTER_LOG_FILE=‘master2-bin.001‘,
   ->   MASTER_LOG_POS=4,
   ->   MASTER_CONNECT_RETRY=10;
Query OK, 0 rows affected (0.00 sec)

4.查看下SLAVE STATUS

MariaDB [(none)]> SHOW SLAVE STATUS\G;
*************************** 1. row ***************************
              Slave_IO_State:
                 Master_Host: master2.mycompany.com
                 Master_User: replication
                 Master_Port: 3306
               Connect_Retry: 10
             Master_Log_File: master2-bin.001
         Read_Master_Log_Pos: 4
              Relay_Log_File: mariadb-relay-bin.000001
               Relay_Log_Pos: 4
       Relay_Master_Log_File: master2-bin.001
            Slave_IO_Running: No
           Slave_SQL_Running: No
      ...以下省略...

5.启动复制线程

MariaDB [(none)]> START SLAVE;

6.再次查看SLAVE STATUS

MariaDB [(none)]> SHOW SLAVE STATUS\G;
*************************** 1. row ***************************
              Slave_IO_State: Connecting to master
                 Master_Host: master2.mycompany.com
                 Master_User: replication
                 Master_Port: 3306
               Connect_Retry: 10
             Master_Log_File: master2-bin.001
         Read_Master_Log_Pos: 4
              Relay_Log_File: mariadb-relay-bin.000001
               Relay_Log_Pos: 4
       Relay_Master_Log_File: master2-bin.001
            Slave_IO_Running: Connecting
           Slave_SQL_Running: Yes
      ...以下省略...

线程已经正常启动
主服务器导入数据进行测试

[[email protected] ~]# mysql < hellodb_innodb.sql
[[email protected] ~]# mysql -e "SHOW DATABASES;"
+--------------------+
| Database           |
+--------------------+
| information_schema |
| hellodb            |
| mysql              |
| performance_schema |
| test               |
+--------------------+

从服务器查看是否同步(CHANGE MASTER TO信息不对怎么可能同步)

MariaDB [(none)]> SHOW DATABASES;
+--------------------+
| Database           |
+--------------------+
| information_schema |
| mysql              |
| performance_schema |
| test               |
+--------------------+
4 rows in set (0.00 sec)

以下为错误解决方法

由于错误发生在CHANGE MASTER TO所以此处将CHANG MASTER TO部分纠正就行
1.首先将从服务器的复制线程停止

MariaDB [(none)]> STOP SLAVE;
Query OK, 0 rows affected (17.48 sec)

2.将从服务器上的SLAVE信息重置

MariaDB [(none)]> RESET SLAVE;
Query OK, 0 rows affected (0.01 sec)

3.重新输入正确的CHANGE MASTER TO信息

MariaDB [(none)]> CHANGE MASTER TO MASTER_HOST=‘192.168.73.110‘,MASTER_USER=‘repluser‘,MASTER_PASSWORD=‘centos‘,MASTER_PORT=3306,MASTER_LOG_FILE=‘mysql-bin.000003‘,MASTER_LOG_POS=245;
Query OK, 0 rows affected (0.01 sec)

4.查看SLAVE STATUS;

MariaDB [(none)]> SHOW SLAVE STATUS\G;
*************************** 1. row ***************************
               Slave_IO_State:
                  Master_Host: 192.168.73.110
                  Master_User: repluser
                  Master_Port: 3306
                Connect_Retry: 10
              Master_Log_File: mysql-bin.000003
          Read_Master_Log_Pos: 245
               Relay_Log_File: mariadb-relay-bin.000001
                Relay_Log_Pos: 4
        Relay_Master_Log_File: mysql-bin.000003
             Slave_IO_Running: No
            Slave_SQL_Running: No
              Replicate_Do_DB:
#此处信息已经改为正确

5.重新启动线程

MariaDB [(none)]> START SLAVE;
Query OK, 0 rows affected (0.00 sec)

6.再次查看SLAVE STATUS;

MariaDB [(none)]> SHOW SLAVE STATUS\G;
*************************** 1. row ***************************
               Slave_IO_State: Waiting for master to send event
                  Master_Host: 192.168.73.110
                  Master_User: repluser
                  Master_Port: 3306
                Connect_Retry: 10
              Master_Log_File: mysql-bin.000003
          Read_Master_Log_Pos: 7384     #已经有数据复制过来了
               Relay_Log_File: mariadb-relay-bin.000002
                Relay_Log_Pos: 7668
        Relay_Master_Log_File: mysql-bin.000003
             Slave_IO_Running: Yes
            Slave_SQL_Running: Yes
#IO和SQL线程已经启动

7.查看下从节点内的库是否已经同步

MariaDB [(none)]> SHOW DATABASES;
+--------------------+
| Database           |
+--------------------+
| information_schema |
| hellodb            |          #hellodb库已经从主节点中复制过来了
| mysql              |
| performance_schema |
| test               |
+--------------------+
5 rows in set (0.01 sec)

其他说明：
如果生产中，发生主从节点之间的数据偏差较大并且迟迟不能同步，可以考虑将从服务器全部清除从新配置从服务器。具体配置方法可以参考https://blog.51cto.com/11886307/2390636

关于sql_slave_skip_counter的使用方法

当发生主键冲突时，从服务器会卡在出错的位置不再进行服务，此种错误一般会出现在主主复制或者从服务器已经占用了某条记录的情况下，此时可以使用此选项来忽略错误。

构建错误

此处继续沿用刚才的主从复制环境
1.在从服务器上创建一条记录

MariaDB [(none)]> INSERT hellodb.teachers VALUE (5,‘Li Xiaolong‘,30,‘M‘);
Query OK, 1 row affected (0.00 sec)

2.在主服务器上也创建一条主键相同的记录

MariaDB [(none)]> INSERT hellodb.teachers VALUE (5,‘Xiao Yan‘,20,‘M‘);
Query OK, 1 row affected (0.00 sec)

3.返回从节点查看SLAVE STATUS

MariaDB [(none)]> SHOW SLAVE STATUS\G;
*************************** 1. row ***************************
               Slave_IO_State: Waiting for master to send event
                  Master_Host: 192.168.73.110
                  Master_User: repluser
                  Master_Port: 3306
                Connect_Retry: 10
              Master_Log_File: mysql-bin.000003
          Read_Master_Log_Pos: 7576
               Relay_Log_File: mariadb-relay-bin.000002
                Relay_Log_Pos: 7668
        Relay_Master_Log_File: mysql-bin.000003
             Slave_IO_Running: Yes
            Slave_SQL_Running: No
              Replicate_Do_DB:
          Replicate_Ignore_DB:
           Replicate_Do_Table:
       Replicate_Ignore_Table:
      Replicate_Wild_Do_Table:
  Replicate_Wild_Ignore_Table:
                   Last_Errno: 1062
                   Last_Error: Could not execute Write_rows event on table hellodb.teachers; Duplicate entry ‘5‘ for key ‘PRIMARY‘, Error_code: 1062; handler error HA_ERR_FOUND_DUPP_KEY; the event‘s master log mysql-bin.000003, end_log_pos 7549
                 Skip_Counter: 0
          Exec_Master_Log_Pos: 7384
              Relay_Log_Space: 8156
              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: NULL
Master_SSL_Verify_Server_Cert: No
                Last_IO_Errno: 0
                Last_IO_Error:
               Last_SQL_Errno: 1062
               Last_SQL_Error: Could not execute Write_rows event on table hellodb.teachers; Duplicate entry ‘5‘ for key ‘PRIMARY‘, Error_code: 1062; handler error HA_ERR_FOUND_DUPP_KEY; the event‘s master log mysql-bin.000003, end_log_pos 7549
  Replicate_Ignore_Server_Ids:
             Master_Server_Id: 1
1 row in set (0.00 sec)

4.从节点已经出错，在主节点继续添加记录

MariaDB [(none)]> INSERT hellodb.teachers VALUE (6,‘Xiao Xuner‘,20,‘M‘);
Query OK, 1 row affected (0.00 sec)

5.此时从节点已经不会再继续从主节点复制信息

MariaDB [(none)]> SELECT * FROM hellodb.teachers WHERE tid>4;
+-----+-------------+-----+--------+
| TID | Name      | Age |Gender |
+-----+-------------+-----+--------+
|   5 | Li Xiaolong |  30 | M      |   #此为刚才从节点添加的记录
+-----+-------------+-----+--------+
1 row in set (0.00 sec)

排错

1.使用sql_slave_skip_counter变量忽略错误

MariaDB [(none)]> SET GLOBAL sql_slave_skip_counter=1;
Query OK, 0 rows affected (0.00 sec)

2.停止线程并重新启动

MariaDB [(none)]> STOP SLAVE;
Query OK, 0 rows affected (0.00 sec)

MariaDB [(none)]> START SLAVE;
Query OK, 0 rows affected (0.00 sec)

3.查看slave status状态，此时已经没有报错的信息

MariaDB [(none)]> SHOW SLAVE STATUS\G;
*************************** 1. row ***************************
               Slave_IO_State: Waiting for master to send event
                  Master_Host: 192.168.73.110
                  Master_User: repluser
                  Master_Port: 3306
                Connect_Retry: 10
              Master_Log_File: mysql-bin.000003
          Read_Master_Log_Pos: 7770
               Relay_Log_File: mariadb-relay-bin.000003
                Relay_Log_Pos: 529
        Relay_Master_Log_File: mysql-bin.000003
             Slave_IO_Running: Yes
            Slave_SQL_Running: Yes
              Replicate_Do_DB:
          Replicate_Ignore_DB:
           Replicate_Do_Table:
       Replicate_Ignore_Table:
      Replicate_Wild_Do_Table:
  Replicate_Wild_Ignore_Table:
                   Last_Errno: 0
                   Last_Error:
                 Skip_Counter: 0
          Exec_Master_Log_Pos: 7770
              Relay_Log_Space: 8634
              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:
  Replicate_Ignore_Server_Ids:
             Master_Server_Id: 1
1 row in set (0.00 sec)

4.在从服务器上查看teachers表

MariaDB [(none)]> SELECT * FROM hellodb.teachers WHERE tid>4;
+-----+-------------+-----+--------+
| TID | Name        | Age | Gender |
+-----+-------------+-----+--------+
|   5 | Li Xiaolong |  30 | M      |
|   6 | Xiao Xuner  |  20 | M      |    #此时刚才在主节点插入的6号记录已经复制过来
+-----+-------------+-----+--------+
2 rows in set (0.00 sec)

以上为主从复制时出错的一些相关的修复方法

原文地址：https://blog.51cto.com/11886307/2390709

时间： 2024-10-12 22:32:29

MySQL主从复制出错的解决方法的相关文章

MySQL数据库ab主从复制出错及解决过程

MySQL数据库ab主从复制出错及解决过程 一.mysql主从服务器报错描述:Slave_IO_Running=NO,Slave_SQL_Running=YES,Last_Errno=0 mysql slave stop ; mysql slave start; mysql show slave status ; 如果Slave_IO_Running=YES ...解决过程 :1 如果:Slave_IO_Running=NO,Slave_SQL_Running=YES,Last_Errno=0m

mysql 主从复制延迟及解决

qps 每秒处理的查询数tps 每秒处理的事务数IOPS,每秒磁盘进行的I/O操作次数 一 延迟的原因 主库并发量大,而从库复制是单线程,从库过多,主从系统配置不当,cpu,内存等,慢sql过大多,大的事物,网络延迟,跨公网的主从复制很容易导致主从复制延迟 二解决方法 1.适当数量的从库,3-5个,从库配置更好的硬件,网络配置等 2.将大事物拆分成多个小事物进行提交,表加主键,否在会全表扫描 3.mysql 5.7.19 + 版本支持并行复制 # slave 从表配置 slave-paralle

今天用pro安装nginx+php+mysql出现问题的解决方法

今天用pro安装nginx+php+mysql出现问题的解决方法 by 伍雪颖 dyld: Library not loaded: @@[email protected]@/openssl/1.0.1h/lib/libcrypto.1.0.0.dylib Referenced from: /usr/local/opt/openssl/lib/libssl.1.0.0.dylib Reason: image not found 解决方法:重装openssl Starting MySQL . ERR

错误：“Cannot load JDBC driver class 'com.mysql.jdbc.Driver”的解决方法

"Cannot load JDBC driver class 'com.mysql.jdbc.Driver " 表示没有JDBC连接MySql的驱动包,因此需要手动添加驱动包到WEB-INF目录下的lib目录中. 解决方法: 从网上下载mysql-connector-java.jar,将其放到"D:\workspace\my-web\src\main\webapp\WEB-INF\lib"目录下,即可解决上述问题. 错误:"Cannot load JDBC

数据库出错的解决方法

1.SQLServer2008数据库sa账户登录127.0.0.1失败 http://wenku.baidu.com/link?url=FiTOMHmOBYJp3LFKYFuHNN2uHn_00zSVbVLgudRa9QA2usB5liFjQbKah4F9GcqUfgWQiMfxDwx9-6kyFnAaaTd9PR72S-ZOuKR_CxJxETW&qq-pf-to=pcqq.c2c 2.SqlServer配置管理器中的sql服务    远程过程调用失败 http://wenku.baidu.c

mysql error nr.1045 解决方法

源地址:http://yanshuaijun.2010.blog.163.com/blog/static/362411622011102443056225/ 主题:mysql error nr.1045 解决方法 2011-11-24 16:30:56|  分类: mysql|举报|字号 订阅 1.进入cmd手动停止mysql服务:net stop mysql. 2.修改C:\Program Files\MySQL\MySQL Server 5.1\ 目录下的my.ini文件,在[mysqld]

c#写入Mysql中文显示乱码 解决方法 z

mysql字符集utf8,c#写入中文后,全部显示成?,一个汉字对应一个? 解决方法:在数据库连接字符串中增加字符集的说明,Charset=utf8,如 MySQLConnection con = new MySQLConnection("server=127.0.0.1;uid=root;pwd=;database=test;Charset=utf8"); 搞定 c#写入Mysql中文显示乱码 解决方法 z,布布扣,bubuko.com

GetDirectories 出错的解决方法

我想找到D盘里面所有 "*.pst文件,类似 windows 下的磁盘搜索功能, using System.IO; Directory.GetFiles(@"d:\", "*.pst", SearchOption.AllDirectories) 测试环境为win7 提示说 某某目录没有访问权限. 获得文件属性   File.GetAttributes(dir.FullName).ToString()   没有权限访问的将会有  System  .Hidde

UCenter info: MySQL Query Error的解决方法----For Discuz!

备注: 出现这个问题同时会造成论坛注册,登录和发帖时等页面无法跳转(APP1运行不正常) 案例: UCenter info: MySQL Query Error SQL:SELECT * FROM [Table]notelist WHEREclosed='0' AND app1<'1' AND app1>'-5' LIMIT 1 Error:Unknown column 'app1' in 'whereclause' Errno:1054 分析: 错误是说在UCenter数据库的notelis