The Ultimate Guide to High Availability with MariaDB
This is a read-only copy of the MariaDB Knowledgebase generated on 2024-11-16. For the latest, interactive version please visit https://mariadb.com/kb/.

How to tell if replication is working

I have a master to slave replication setup. The slave is running Mariadb 10.0.32 on Centos 6. The master is Clustrix ( a clustered MySQL 5 compatible product)>

I am not seeing any errors in "show slave status". The output is below. Running "show slave status" in succession show change in "Read_Master_Log_Pos" and "Relay_Log_Space". However, the value for "Exec_Master_Log_Pos" does NOT change. In addition, it does NOT appear that any inserts/ updates are occurring on the slave.

The following maybe relevant (my knowledge of this process is somewhat limited) The database to be replicated is about 2.5TB and it was necessary to use mysqldump to obtain a backup and then populate the slave. This process took about 3 and half days. The dump used to populate the database had a MASTER_LOG_FILE='dr_ladders.001270', MASTER_LOG_POS=20857072 The binlog file on the master when I started the slave was dr_ladders.001328

Finally, the one and only error that is occurring repeatedly in the log is: Slave SQL: Could not execute Delete_rows_v1 event on table ladders.subscriber_parameter_log; Can't find record in 'subscriber_parameter_log', Error_code: 1032; Can't find record in 'subscriber_parameter_log', Error_code: 1032; Can't find record in 'subscriber_parameter_log', Error_code: 1032 I do have "slave-skip-errors" for 1032.

Thanks in advance for your help.

show slave status\G$
*************************** 1. row ***************************$
               Slave_IO_State: Waiting for master to send event$
                  Master_Host: 10.14.4.4$
                  Master_User: rep_mariadb$
                  Master_Port: 3306$
                Connect_Retry: 10$
              Master_Log_File: dr_ladders.001330$
          Read_Master_Log_Pos: 43841364$
               Relay_Log_File: ip-10-14-11-198-relay-bin.000002$
                Relay_Log_Pos: 3913332$
        Relay_Master_Log_File: dr_ladders.001270$
             Slave_IO_Running: Yes$
            Slave_SQL_Running: Yes$
              Replicate_Do_DB: ladders$
          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: 24770010$
              Relay_Log_Space: 6590196062$
              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: 366210$
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: 1133397644$
               Master_SSL_Crl: $
           Master_SSL_Crlpath: $
                   Using_Gtid: No$
                  Gtid_IO_Pos: $
1 row in set (0.00 sec)$

Answer Answered by Ian Gilfillan in this comment.

It appears replication is working, but there is a huge lag (it is 366210 seconds behind the master, over 4 days).

The query in your error log is failing, but with slave-skip-errors this won't hold up things.

Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.