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

Corrupted replication event was detected. Not printing the value

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Duplicate
    • 10.1.23
    • N/A
    • Replication
    • None
    • 10.1.23 enterprise
       
      binlog_format = ROW

      # mysqlbinlog mysql-bin.000001 --version
      mysqlbinlog Ver 3.3 for Linux at x86_64

    Description

      mysqlbinlog -vv --base64-output=decode-rows mysql-bin.000001 | grep 'Corrupted' | more
      ###   @4=***Corrupted replication event was detected. Not printing the value***
      ###   @3=***Corrupted replication event was detected. Not printing the value***
      ###   @1=***Corrupted replication event was detected. Not printing the value***
      ###   @5=***Corrupted replication event was detected. Not printing the value***
      ###   @4=***Corrupted replication event was detected. Not printing the value***
      ###   @3=***Corrupted replication event was detected. Not printing the value***
      ###   @2=***Corrupted replication event was detected. Not printing the value***
      ###   @2=***Corrupted replication event was detected. Not printing the value***
      ###   @1=***Corrupted replication event was detected. Not printing the value***
      ###   @4=***Corrupted replication event was detected. Not printing the value***
      ###   @1=***Corrupted replication event was detected. Not printing the value***
      ###   @5=***Corrupted replication event was detected. Not printing the value***
      ###   @6=***Corrupted replication event was detected. Not printing the value***
      ###   @2=***Corrupted replication event was detected. Not printing the value***
      ###   @4=***Corrupted replication event was detected. Not printing the value***
      ###   @3=***Corrupted replication event was detected. Not printing the value***
      ###   @3=***Corrupted replication event was detected. Not printing the value***
      ###   @1=***Corrupted replication event was detected. Not printing the value***
      ###   @3=***Corrupted replication event was detected. Not printing the value***
      ###   @5=***Corrupted replication event was detected. Not printing the value***
      ###   @4=***Corrupted replication event was detected. Not printing the value***
      ###   @3=***Corrupted replication event was detected. Not printing the value***
      

      Attachments

        Issue Links

          Activity

            hiller1 hiller1 added a comment -

            I have uploaded to FTP. The file name is Corrupted_binlog_hiller1.tgz

            THANKS

            hiller1 hiller1 added a comment - I have uploaded to FTP. The file name is Corrupted_binlog_hiller1.tgz THANKS

            Thank you.
            You have indicated version 10.1.23, but the binary log actually says 10.0.25. Is it possible that you have replication from 10.0 to 10.1?
            If so, possibly you have encountered the problem described in MDEV-5377 and issues linked to it. Does it look likely, given your configuration and table structures?

            elenst Elena Stepanova added a comment - Thank you. You have indicated version 10.1.23, but the binary log actually says 10.0.25. Is it possible that you have replication from 10.0 to 10.1? If so, possibly you have encountered the problem described in MDEV-5377 and issues linked to it. Does it look likely, given your configuration and table structures?
            hiller1 hiller1 added a comment -

            YES,I have replication from 10.0 to 10.1, 10.0 is master, 10.1 is slave, replicate is OK.

            table structures:
            `create_time` timestamp(6) NOT NULL DEFAULT CURRENT_TIMESTAMP(6),
            `update_time` timestamp(6) NOT NULL DEFAULT CURRENT_TIMESTAMP(6) ON UPDATE CURRENT_TIMESTAMP(6),

            10.0 insert result:
            create_time
            2017-05-22 00:00:49.000000
            2017-05-22 00:01:04.000000
            2017-05-22 00:01:27.000000

            hiller1 hiller1 added a comment - YES,I have replication from 10.0 to 10.1, 10.0 is master, 10.1 is slave, replicate is OK. table structures: `create_time` timestamp(6) NOT NULL DEFAULT CURRENT_TIMESTAMP(6), `update_time` timestamp(6) NOT NULL DEFAULT CURRENT_TIMESTAMP(6) ON UPDATE CURRENT_TIMESTAMP(6), 10.0 insert result: create_time 2017-05-22 00:00:49.000000 2017-05-22 00:01:04.000000 2017-05-22 00:01:27.000000

            Since the binary log was produced by 10.0 server, it is indeed the same problem as MDEV-5377 – or, more precisely, MDEV-9567, which has the same root cause as MDEV-5377.

            You can track further progress in MDEV-5377.

            elenst Elena Stepanova added a comment - Since the binary log was produced by 10.0 server, it is indeed the same problem as MDEV-5377 – or, more precisely, MDEV-9567 , which has the same root cause as MDEV-5377 . You can track further progress in MDEV-5377 .
            hiller1 hiller1 added a comment -

            THANKS!

            hiller1 hiller1 added a comment - THANKS!

            People

              Unassigned Unassigned
              hiller1 hiller1
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

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