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

Replica stops with "Found invalid event in binary log"

    XMLWordPrintable

Details

    • Bug
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • 10.4.25, 10.6.9
    • 10.4
    • Replication
    • None

    Description

      I got a strange behaviour with replication
      Sometimes (I can't reproduce ) the replica stops IO_thread with next error in the log

      2022-11-08 13:56:47 87893133 [ERROR] Read invalid event from master: 'Found invalid event in binary log', master could be corrupt but a more likely cause of this is a bug
      2022-11-08 13:56:47 87893133 [ERROR] Slave I/O: Relay log write failure: could not queue event from master, Internal MariaDB error code: 1595
      2022-11-08 13:56:47 87893133 [Note] Slave I/O thread exiting, read up to log 'mysqld-bin.202006', position 4; GTID position 11-11-48058108793
      

      The errors always appear at position 4 , at the start of binlog.
      The queries in 11-11-48058108793 and previous statement looks as correct insert/update requests

      The replication begins to work after restart replications `stop slave; start slave`

      I've attached config file

      Attachments

        Activity

          People

            bnestere Brandon Nesterenko
            R Anton
            Votes:
            1 Vote for this issue
            Watchers:
            8 Start watching this issue

            Dates

              Created:
              Updated:

              Git Integration

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