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

Galera test failure on MTR tests galera.galera_gcache_recover_manytrx and galera_sr.MDEV-27615, galera.galera_gcache_recover_manytrx

    XMLWordPrintable

Details

    • Bug
    • Status: Stalled (View Workflow)
    • Major
    • Resolution: Unresolved
    • 11.1.1, 11.0(EOL)
    • 11.0(EOL)
    • Galera
    • None

    Description

      MTR test : galera.galera_gcache_recover_manytrx

      ==============================================================================
       
      TEST                                      RESULT   TIME (ms) or COMMENT
      --------------------------------------------------------------------------
       
      worker[1]  - 'localhost:16000' was not free
      worker[1] Using MTR_BUILD_THREAD 301, with reserved ports 16020..16039
      galera.galera_gcache_recover_manytrx 'innodb' [ fail ]
              Test ended at 2023-05-17 08:55:09
       
      CURRENT_TEST: galera.galera_gcache_recover_manytrx
      mysqltest: At line 146: query 'reap' failed with wrong errno <Unknown> (2026): 'TLS/SSL error: The TLS connection was non-properly terminated.', instead of <Unknown> (2013)...
       
      The result from queries just before the failure was:
      < snip >
      CALL insert_simple();;
      connection node_1_insert_multi;
      CALL insert_multi();;
      connection node_1_insert_transaction;
      CALL insert_transaction ();;
      connection node_1_update_simple;
      CALL update_simple ();;
      connection node_1_insert_1k;
      CALL insert_1k ();;
      connection node_1_insert_1m;
      CALL insert_1m ();;
      connection node_1_insert_10m;
      CALL insert_10m ();;
      connection node_2;
      call mtr.add_suppression("Error in Log_event::read_log_event():.*");
      SET SESSION wsrep_sync_wait = 0;
      Killing server ...
      connection node_1;
      Killing server ...
      connection node_1_insert_simple;
      

      MTR test : galera_sr.MDEV-27615

      ==============================================================================
       
      TEST                                      RESULT   TIME (ms) or COMMENT
      --------------------------------------------------------------------------
       
      worker[1]  - 'localhost:16000' was not free
      worker[1] Using MTR_BUILD_THREAD 301, with reserved ports 16020..16039
      galera_sr.MDEV-27615 'innodb'            [ fail ]
              Test ended at 2023-05-17 09:05:01
       
      CURRENT_TEST: galera_sr.MDEV-27615
      mysqltest: At line 47: query 'reap' failed with wrong errno <Unknown> (2026): 'TLS/SSL error: The TLS connection was non-properly terminated.', instead of <Unknown> (2013)...
       
      The result from queries just before the failure was:
      connection node_2;
      connection node_1;
      connection node_1;
      connection node_2;
      connect node_2a, 127.0.0.1, root, , test, $NODE_MYPORT_2;
      connection node_2;
      CREATE TABLE t1 (f1 INTEGER PRIMARY KEY) Engine=InnoDB;
      SET DEBUG_SYNC='wsrep_before_fragment_certification SIGNAL before_fragment WAIT_FOR continue';
      SET SESSION wsrep_trx_fragment_size=1;
      START TRANSACTION;
      INSERT INTO t1 VALUES (1);;
      connection node_2a;
      SET SESSION wsrep_sync_wait = 0;
      SET DEBUG_SYNC='now WAIT_FOR before_fragment';
      SET GLOBAL wsrep_cluster_address = '';
      SET DEBUG_SYNC = 'now SIGNAL continue';
      connection node_2;
      
      

      Attachments

        1. logs (8).tar.gz
          9.83 MB
          Timofey Turenko
        2. mtr (8).log
          92 kB
          Timofey Turenko

        Activity

          People

            sysprg Julius Goryavsky
            ramesh Ramesh Sivaraman
            Votes:
            0 Vote for this issue
            Watchers:
            2 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.