代码之家  ›  专栏  ›  技术社区  ›  Mustermann

mariadb:中继日志写入失败

  •  2
  • Mustermann  · 技术社区  · 7 年前

    我目前正试图让一个MariaDB 10.2.9作为mysql 5.5主服务器的从属服务器运行,但我一直收到相同的错误(Last\u IO\u Errno:1595,中继日志写入失败:无法将来自主服务器的事件排队)

    由于主版本和从版本之间存在一些差异,我必须设置

    set global binlog_checksum='NONE';
    

    总而言之,我取了一个mysqldump的主文件,读了log\u pos/文件,然后

    SET GLOBAL server_id=2;
    CHANGE MASTER TO 
    MASTER_HOST='10.145.46.11',MASTER_USER='replicant',MASTER_PASSWORD='...', 
    MASTER_LOG_FILE='mysql-bin.000042', MASTER_LOG_POS=107;
    start slave;
    

    ...
    2017-10-31 11:44:41 140026338711296 [Note] Slave SQL thread initialized, starting replication in log 'mysql-bin.000007' at position 107, relay log './mariadb-relay-bin.000001' position: 4
    2017-10-31 11:44:41 140027007977216 [Note] Slave I/O thread: connected to master 'replicant@10.145.46.11:3306',replication started in log 'mysql-bin.000007' at position 107
    2017-10-31 11:44:42 140027007977216 [Warning] Slave I/O: Notifying master by SET @master_binlog_checksum= @@global.binlog_checksum failed with error: Unknown system variable 'binlog_checksum', Internal MariaDB error code: 1193
    2017-10-31 11:44:42 140027007977216 [ERROR] Slave I/O: Replication event checksum verification failed while reading from network, Internal MariaDB error code: 1743
    2017-10-31 11:44:42 140027007977216 [ERROR] Slave I/O: Relay log write failure: could not queue event from master, Internal MariaDB error code: 1595
    2017-10-31 11:44:42 140027007977216 [Note] Slave I/O thread exiting, read up to log 'mysql-bin.000007', position 107
    ....
    

    我也不确定什么样的校验和在这里失败(mysql参考称为“复制事件校验和”?),我试过:

    set global slave_sql_verify_checksum=0;
    

    MariaDB [(none)]> show slave status \G;
    *************************** 1. row ***************************
                   Slave_IO_State: 
                      Master_Host: 10.145.46.11
                      Master_User: replicant
                      Master_Port: 3306
                    Connect_Retry: 60
                  Master_Log_File: mysql-bin.000007
              Read_Master_Log_Pos: 107
                   Relay_Log_File: mariadb-relay-bin.000001
                    Relay_Log_Pos: 4
            Relay_Master_Log_File: mysql-bin.000007
                 Slave_IO_Running: No
                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: 107
                  Relay_Log_Space: 256
                  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: 1595
                    Last_IO_Error: Relay log write failure: could not queue event from master
                   Last_SQL_Errno: 0
                   Last_SQL_Error: 
      Replicate_Ignore_Server_Ids: 
                 Master_Server_Id: 1
                   Master_SSL_Crl: 
               Master_SSL_Crlpath: 
                       Using_Gtid: No
                      Gtid_IO_Pos: 
          Replicate_Do_Domain_Ids: 
      Replicate_Ignore_Domain_Ids: 
                    Parallel_Mode: conservative
                        SQL_Delay: 0
              SQL_Remaining_Delay: NULL
          Slave_SQL_Running_State: Slave has read all relay log; waiting for the slave I/O thread to update it
    
    1 回复  |  直到 7 年前
        1
  •  3
  •   iBug    7 年前

    我也有同样的问题,发现了一个 answer . 变量 slave_sql_verify_checksum 在配置文件中设置 my.cnf . 设置 slave_sql_verify_checksum = NONE 然后重新启动服务器。