Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-7237

Parallel replication: incorrect relaylog position after stop/start the slave




      141201  8:59:25 [Note] Slave SQL thread initialized, starting replication in log 'mysql-bin.000116' at position 1146, relay log './frigg-relay-bin.000256' position: 1780
      141201  8:59:25 [ERROR] Error in Log_event::read_log_event(): 'Event too big', data_len: 1734964078, event_type: 105
      141201  8:59:25 [ERROR] Error reading relay log event: slave SQL thread aborted because of I/O error
      141201  8:59:25 [ERROR] Slave SQL: Relay log read failure: Could not parse relay log event entry. The possible reasons are: the master's binary log is corrupted (you can check this by running 'mysqlbinlog' on the binary log), the slave's relay log is corrupted (you can check this by running 'mysqlbinlog' on the relay log), a network problem, or a bug in the master's or slave's MySQL code. If you want to check the master's binary log or slave's relay log, you will be able to know their names by issuing 'SHOW SLAVE STATUS' on this slave. Internal MariaDB error code: 1594
      141201  8:59:25 [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.000116' position 1146
      141201  8:59:25 [Note] Slave I/O thread: connected to master 'root@',replication started in log 'mysql-bin.000323' at position 4

      I reproduced this by first preparing a binlog using RQG replication-dml. I
      then setup a master-slave using this binlog. While the slave was running, I
      executed STOP SLAVE and START SLAVE a couple of times, and eventually got this

      This was reproduced in non-GTID mode.

      I had a couple reports of a similar problem from two users. Given the ease of
      reproducing this problem, it seems likely that it is the same as at least some
      of the cases experienced by users.




            knielsen Kristian Nielsen
            knielsen Kristian Nielsen
            0 Vote for this issue
            2 Start watching this issue



              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.