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

galera_bf_lock_wait test failed

    XMLWordPrintable

Details

    Description

      galera.galera_bf_lock_wait test failed with

      mysqltest: At line 65: command "grep 'BF lock wait long' $MYSQLTEST_VARDIR/log/mysqld.*.err" succeeded - should have failed with errno 1...

      More complete log:

      galera.galera_bf_lock_wait 'innodb'      [ fail ]
              Test ended at 2023-11-10 21:24:54
       
      CURRENT_TEST: galera.galera_bf_lock_wait
      mysqltest: At line 65: command "grep 'BF lock wait long' $MYSQLTEST_VARDIR/log/mysqld.*.err" succeeded - should have failed with errno 1...
       
      The result from queries just before the failure was:
      < snip >
      update t1 set b=connection_id() where a=1;
      commit;
      SET current_num = current_num + 1;
      END WHILE;
      END|
      connection node_2;
      connect node_1_p1, 127.0.0.1, root, , test, $NODE_MYPORT_1;
      SET SESSION wsrep_sync_wait=0;
      call p1(1000);
      connect node_1_p2, 127.0.0.1, root, , test, $NODE_MYPORT_1;
      SET SESSION wsrep_sync_wait=0;
      call p1(1000);
      connect node_2_p1, 127.0.0.1, root, , test, $NODE_MYPORT_2;
      SET SESSION wsrep_sync_wait=0;
      call p1(1000);
      connect node_2_p2, 127.0.0.1, root, , test, $NODE_MYPORT_2;
      SET SESSION wsrep_sync_wait=0;
      call p1(1000);
      connection node_1;
      checking error log for 'BF lock wait long' message for 10 times every 10 seconds ...

      Attachments

        Issue Links

          Activity

            People

              sysprg Julius Goryavsky
              sysprg Julius Goryavsky
              Votes:
              1 Vote for this issue
              Watchers:
              3 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.