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

rpl.rpl_start_alter_7 (and 8, mysqbinlog_2) fail in buildbot, [ERROR] Slave SQL: Error during XID COMMIT: failed to update GTID state in mysql.gtid_slave_pos

    XMLWordPrintable

Details

    Description

      https://buildbot.mariadb.org/#/builders/195/builds/4566/steps/7/logs/stdio
      https://buildbot.mariadb.org/#/builders/195/builds/4419/steps/7/logs/stdio

      Occurs for rpl.rpl_start_alter_7, rpl.rpl_start_alter_8, rpl.rpl_start_alter_mysqlbinlog_2, rpl.rpl_start_alter_4, rpl.rpl_start_alter_3, rpl.rpl_start_alter_6, rpl.rpl_start_alter_5

      rpl.rpl_start_alter_7 'innodb'           w1 [ fail ]
              Test ended at 2022-02-15 02:25:31
      CURRENT_TEST: rpl.rpl_start_alter_7
      mysqltest: In included file "./include/sync_with_master_gtid.inc": 
      included from /buildbot/amd64-ubuntu-1804-msan/build/mysql-test/suite/rpl/t/rpl_start_alter_7.test at line 83:
      At line 48: Failed to sync with master
      The result from queries just before the failure was:
      < snip >
      ERROR 23000: Duplicate entry '2' for key 'b'
      ERROR 23000: Duplicate entry '2' for key 'b'
      ERROR 23000: Duplicate entry '2' for key 'b'
      connection server_2;
      drop database s2;
      select @@gtid_binlog_pos;
      @@gtid_binlog_pos
      12-2-412
      connection server_3;
      start all slaves;
      Warnings:
      Note	1937	SLAVE 'm2' started
      Note	1937	SLAVE 'm1' started
      set default_master_connection = 'm1';
      include/wait_for_slave_to_start.inc
      set default_master_connection = 'm2';
      include/wait_for_slave_to_start.inc
      set default_master_connection = 'm1';
      include/sync_with_master_gtid.inc
      Timeout in master_gtid_wait('11-1-412', 120), current slave GTID position is: 11-1-291,12-2-412.
      

      Not checked with the original failures, but the replica error log in the multi-master setup shows:

      2022-11-24  4:29:00 31 [Note] Master 'm1': Slave SQL thread initialized, starting replication in log 'FIRST' at position 4, relay log './mysqld-relay-bin-m1.000001' position: 4; GTID position '12-2-2'
      2022-11-24  4:29:02 24 [ERROR] Slave SQL: Error during XID COMMIT: failed to update GTID state in mysql.gtid_slave_pos: 1062: Duplicate entry '11-605' for key 'PRIMARY', Gtid 11-1-281, Internal MariaDB error code: 1942
      2022-11-24  4:29:02 24 [ERROR] Slave (additional info): Duplicate entry '11-605' for key 'PRIMARY' Error_code: 1062
      2022-11-24  4:29:02 24 [Warning] Slave: Duplicate entry '11-605' for key 'PRIMARY' Error_code: 1062
      2022-11-24  4:29:02 24 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'master-bin.000001' position 49198; GTID position '11-1-280,12-2-334'
      2022-11-24  4:29:02 31 [Note] Master 'm1': Slave SQL thread exiting, replication stopped in log 'master-bin.000001' at position 49198; GTID position '11-1-280,12-2-334', master: 127.0.0.1:16040
      

      Attachments

        1. logs.tar.gz
          1.13 MB
        2. MDEV-27849.cnf
          0.7 kB
        3. MDEV-27849.test
          2 kB

        Issue Links

          Activity

            People

              knielsen Kristian Nielsen
              angelique.sklavounos Angelique Sklavounos (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 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.