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

RBR from binary(16) to inet6 fails with error 171: The event was corrupt, leading to illegal data being read

Details

    Description

      The test case mainly represents upgrade through replication (old master => new slave), where the old master had a table with binary(16) for IPv6 values, while the new slave has inet6.

      --source include/have_binlog_format_row.inc
      		 
      --source include/master-slave.inc
      		 
       
      		 
      create table t1 (a binary(16));
      		 
       
      		 
      --sync_slave_with_master
      		 
      alter table t1 modify a inet6;
      		 
       
      		 
      --connection master
      		 
      insert into t1 values (inet6_aton('::'));
      		 
       
      		 
      --sync_slave_with_master
      		 
       
      		 
      # Cleanup
      		 
      --connection master
      		 
      drop table t1;
      		 
      --source include/rpl_end.inc

      10.5 22b645ef

      		 
      Last_Errno	1030
      		 
      Last_Error	Could not execute Write_rows_v1 event on table test.t1; Got error 171 "The event was corrupt, leading to illegal data being read" from storage engine MyISAM, Error_code: 1030; handler error HA_ERR_CORRUPT_EVENT; the event's master log master-bin.000001, end_log_pos 655

      Attachments

        Issue Links

          relates to

          Task - A task that needs to be done. MDEV-274 The data type for IPv6/IPv4 addresses in MariaDB

          • Major - Major loss of function.
          • Closed

          Task - A task that needs to be done. MDEV-20784 Testing for MDEV-274 (INET6, data type for IPv6/IPv4 addresses)

          • Major - Major loss of function.
          • Closed

          Activity

            bar Alexander Barkov added a comment -

            The problem happens because the master uses suffix compression for BINARY(16) and therefore removes trailing 0x00 bytes, while the slave expects exactly 16 bytes.

            Field_inet6::unpack() should be extended to handle this.

            bar Alexander Barkov added a comment - The problem happens because the master uses suffix compression for BINARY(16) and therefore removes trailing 0x00 bytes, while the slave expects exactly 16 bytes. Field_inet6::unpack() should be extended to handle this.

            People

              bar Alexander Barkov
              elenst Elena Stepanova
              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.