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

Replication from MySQL 5.7 Master to MariaDB 10.6 Galera Cluster breaks

    XMLWordPrintable

Details

    Description

      When we try to migrate from MySQL 5.7 to a MariaDB 10.6 Galera Cluster using the Master/Slave replication the Galera Cluster immediately falls apart after the first CREATE DATABASE statement.

      How to reproduce:

      On Master:

      CREATE DATABASE xyz;

      root@localhost [(none)]> show databases;
      --------------------

      Database

      --------------------

      dcz01

      --------------------

      On Galera Slave node the database is there but Cluster falls apart immediately:

      wsrep_local_state_comment Inconsistent

      and the database is NOT on the other Galera nodes... This breaks our whole migration path from MySQL to MariaDB.

      In the error log we can see:

      2024-06-17 11:40:18 2 [ERROR] Error in Log_event::read_log_event(): 'Found invalid event in binary log', data_len: 42, event_type: -94
      2024-06-17 11:40:18 2 [ERROR] WSREP: applier could not read binlog event, seqno: 5, len: 89
      2024-06-17 11:40:18 0 [Note] WSREP: Member 1(Node B) initiates vote on 0b50568a-2c8d-11ef-9802-aefa615882bd:5,f5d8d0c5de6f861a:
      2024-06-17 11:40:18 0 [Note] WSREP: Votes over 0b50568a-2c8d-11ef-9802-aefa615882bd:5:
      f5d8d0c5de6f861a: 1/3
      Waiting for more votes.
      2024-06-17 11:40:18 8 [Note] WSREP: Got vote request for seqno 0b50568a-2c8d-11ef-9802-aefa615882bd:5
      2024-06-17 11:40:18 0 [Note] WSREP: Member 0(Node A) responds to vote on 0b50568a-2c8d-11ef-9802-aefa615882bd:5,0000000000000000: Success
      2024-06-17 11:40:18 0 [Note] WSREP: Votes over 0b50568a-2c8d-11ef-9802-aefa615882bd:5:
      0000000000000000: 1/3
      f5d8d0c5de6f861a: 1/3
      Waiting for more votes.
      2024-06-17 11:40:18 0 [Note] WSREP: Member 2(Node C) initiates vote on 0b50568a-2c8d-11ef-9802-aefa615882bd:5,f5d8d0c5de6f861a:
      2024-06-17 11:40:18 0 [Note] WSREP: Votes over 0b50568a-2c8d-11ef-9802-aefa615882bd:5:
      0000000000000000: 1/3
      f5d8d0c5de6f861a: 2/3
      Winner: f5d8d0c5de6f861a
      2024-06-17 11:40:18 2 [Note] WSREP: Closing send monitor...
      2024-06-17 11:40:18 2 [Note] WSREP: Closed send monitor.
      2024-06-17 11:40:18 2 [Note] WSREP: gcomm: terminating thread
      2024-06-17 11:40:18 2 [Note] WSREP: gcomm: joining thread
      2024-06-17 11:40:18 2 [Note] WSREP: gcomm: closing backend
      2024-06-17 11:40:21 2 [Note] WSREP: (7fc038cb-9b5c, 'tcp://127.0.0.1:5695') connection to peer 0b4f063d-bd81 with addr tcp://127.0.0.1:5691 timed out, no messages seen in PT3S, socket stats: rtt: 6169 rttvar: 10622 rto: 208000 lost: 0 last_data_recv: 3196 cwnd: 10 last_queued_since: 196794910 last_delivered_since: 3196690121 send_queue_length: 0 send_queue_bytes: 0 segment: 0 messages: 0
      2024-06-17 11:40:21 2 [Note] WSREP: (7fc038cb-9b5c, 'tcp://127.0.0.1:5695') turning message relay requesting on, nonlive peers: tcp://127.0.0.1:5691
      2024-06-17 11:40:23 2 [Note] WSREP: (7fc038cb-9b5c, 'tcp://127.0.0.1:5695') reconnecting to 0b4f063d-bd81 (tcp://127.0.0.1:5691), attempt 0

      mariadb-binlog --verbose GRA_2_5_v2.log

      1. at 256
        #240617 11:40:18 server id 3330 end_log_pos 252 CRC32 0xd7ae83ad Start: binlog v 4, server v 10.6.17-MariaDB-log created 240617 11:40:18 at startup
        ROLLBACK/!/;
        BINLOG '
        ggRwZg8CDQAA/AAAAPwAAAAAAAQAMTAuNi4xNy1NYXJpYURCLWxvZwAAAAAAAAAAAAAAAAAAAAAA
        AAAAAAAAAAAAAAAAAACCBHBmEzgNAAgAEgAEBAQEEgAA5AAEGggAAAAICAgCAAAACgoKAAAAAAAA
        AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
        AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
        AAAAAAAAAAAEEwQADQgICAoKCgGtg67X
        '/!/;
        ERROR: Error in Log_event::read_log_event(): 'Found invalid event in binary log', data_len: 42, event_type: 162
        ERROR: Could not read entry at offset 508: Error in log format or read error.

      mariadb-binlog chef-relay-bin.000002

      1. at 419
        #240617 11:40:18 server id 42 end_log_pos 670 CRC32 0x55166dfd Query thread_id=5 exec_time=0 error_code=0 xid=0
        SET TIMESTAMP=1718617218/!/;
        SET @@session.pseudo_thread_id=5/!/;
        SET @@session.foreign_key_checks=1, @@session.sql_auto_is_null=0, @@session.unique_checks=1, @@session.autocommit=1, @@session.check_constraint_checks=1/!/;
        SET @@session.sql_mode=1436549152/!/;
        SET @@session.auto_increment_increment=1, @@session.auto_increment_offset=1/!/;
        /Unable to render embedded object: File (\C utf8mb3 *//*) not found./;
        SET @@session.character_set_client=utf8mb3,@@session.collation_connection=33,@@session.collation_server=8/!/;
        SET @@session.lc_time_names=0/!/;
        SET @@session.collation_database=DEFAULT/!/;
        create database dcz01
        /!/;
        DELIMITER ;
      2. End of log file
        ROLLBACK /* added by mysqlbinlog */;
        /!50003 SET COMPLETION_TYPE=@OLD_COMPLETION_TYPE/;
        /!50530 SET @@SESSION.PSEUDO_SLAVE_MODE=0/;

      There is another minor error:
      event_type: -94 -> this should not be UNSIGNED but SIGNED (162)

      We can reproduce it at will (we have done it twice).

      Attachments

        Issue Links

          Activity

            People

              janlindstrom Jan Lindström
              oli Oli Sennhauser
              Votes:
              0 Vote for this issue
              Watchers:
              4 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.