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

Test rpl.rpl_semi_sync_master_shutdown Failures

    XMLWordPrintable

Details

    • Bug
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • 11.3.2, 10.5.25, 10.6.18, 10.11.8, 11.0.6, 11.1.5, 11.2.4
    • 10.5
    • Replication, Tests
    • None

    Description

      It can fail with the wrong error code:

      rpl.rpl_semi_sync_master_shutdown 'stmt' w12 [ fail ]
              Test ended at 2024-06-06 08:47:27
       
      CURRENT_TEST: rpl.rpl_semi_sync_master_shutdown
      mysqltest: In included file "./include/wait_for_slave_io_error.inc": 
      included from /home/buildbot/amd64-fedora-38-last-N-failed/build/mysql-test/suite/rpl/t/rpl_semi_sync_master_shutdown.test at line 36: 
      At line 72: Slave stopped with wrong error code
       
      The result from queries just before the failure was:
      < snip >
      ERROR HY000: Server has gone away
       
      **** SHOW BINARY LOGS on server_1 ****
      SHOW BINARY LOGS;
      ERROR HY000: Server has gone away
       
      **** SHOW BINLOG EVENTS on server_1 ****
      ERROR HY000: Server has gone away
      binlog_name = ''
      SHOW BINLOG EVENTS IN ''; 
      ERROR HY000: Server has gone away
       
      **** SHOW RELAYLOG EVENTS on server_1 ****
      ERROR HY000: Server has gone away
      relaylog_name = ''
      SHOW RELAYLOG EVENTS IN ''; 
      ERROR HY000: Server has gone away
      ERROR HY000: Server has gone away
      connection slave;
      **** Slave stopped with wrong error code: 2013 (expected 2003) ****
       
      More results from queries before failure can be found in /home/buildbot/amd64-fedora-38-last-N-failed/build/mysql-test/var/12/log/rpl_semi_sync_master_shutdown.log
      

      As well as a timeout while waiting for the slave to start

      rpl.rpl_semi_sync_master_shutdown 'row'  w9 [ fail ]
              Test ended at 2024-05-30 20:19:32
       
      CURRENT_TEST: rpl.rpl_semi_sync_master_shutdown
      mysqltest: In included file "./include/wait_for_slave_param.inc": 
      included from ./include/wait_for_slave_io_to_start.inc at line 41:
      included from /home/buildbot/amd64-debian-11-aocc/build/mysql-test/suite/rpl/t/rpl_semi_sync_master_shutdown.test at line 50:
      At line 111: Timeout in include/wait_for_slave_param.inc
       
      The result from queries just before the failure was:
      < snip >
       
      **** SHOW BINARY LOGS on server_1 ****
      SHOW BINARY LOGS;
      Log_name	File_size
      master-bin.000001	736
      master-bin.000002	343
       
      **** SHOW BINLOG EVENTS on server_1 ****
      binlog_name = 'master-bin.000002'
      SHOW BINLOG EVENTS IN 'master-bin.000002';
      Log_name	Pos	Event_type	Server_id	End_log_pos	Info
      master-bin.000002	4	Format_desc	1	256	Server ver: 11.5.2-MariaDB-log, Binlog ver: 4
      master-bin.000002	256	Gtid_list	1	299	[0-1-2]
      master-bin.000002	299	Binlog_checkpoint	1	343	master-bin.000002
       
      **** SHOW RELAYLOG EVENTS on server_1 ****
      relaylog_name = 'No such row'
      SHOW RELAYLOG EVENTS IN 'No such row';
      Log_name	Pos	Event_type	Server_id	End_log_pos	Info
      connection slave;
       
      More results from queries before failure can be found in /home/buildbot/amd64-debian-11-aocc/build/mysql-test/var/9/log/rpl_semi_sync_master_shutdown.log
       
       - saving '/home/buildbot/amd64-debian-11-aocc/build/mysql-test/var/9/log/rpl.rpl_semi_sync_master_shutdown-row/' to '/home/buildbot/amd64-debian-11-aocc/build/mysql-test/var/log/rpl.rpl_semi_sync_master_shutdown-row/'
      

      Attachments

        Activity

          People

            bnestere Brandon Nesterenko
            bnestere Brandon Nesterenko
            Votes:
            0 Vote for this issue
            Watchers:
            3 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.