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

Test failure on galera.galera_pc_ignore_sb

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Won't Fix
    • 10.1(EOL)
    • N/A
    • Galera, Tests
    • None

    Description

      Surfaced after galera library upgrade:

      galera.galera_pc_ignore_sb 'innodb_plugin' w4 [ fail ]
              Test ended at 2018-10-01 09:44:31
       
      CURRENT_TEST: galera.galera_pc_ignore_sb
      mysqltest: At line 38: query 'SET GLOBAL wsrep_provider_options = '$wsrep_provider_options_orig';' failed: 1210: Incorrect arguments to SET
       
      The result from queries just before the failure was:
      SET GLOBAL wsrep_provider_options = 'pc.ignore_sb=true';
      Killing server ...
      CREATE TABLE t1 (f1 INTEGER) ENGINE=InnoDB;
      INSERT INTO t1 VALUES (1);
      DROP TABLE t1;
      SELECT VARIABLE_VALUE = 1 FROM INFORMATION_SCHEMA.GLOBAL_STATUS WHERE VARIABLE_NAME = 'wsrep_cluster_size';
      VARIABLE_VALUE = 1
      1
      SELECT VARIABLE_VALUE = 'ON' FROM INFORMATION_SCHEMA.GLOBAL_STATUS WHERE VARIABLE_NAME = 'wsrep_ready';
      VARIABLE_VALUE = 'ON'
      1
      SET GLOBAL wsrep_cluster_address = '';
      

      Attachments

        Issue Links

          Activity

            After several tries had to give up current version:

            http://buildbot.askmonty.org/buildbot/builders/kvm-rpm-centos74-amd64/builds/4633/steps/mtr/logs/stdio

            galera.galera_pc_ignore_sb 'innodb_plugin' w4 [ fail ]
                    Test ended at 2018-10-03 17:31:50
             
            CURRENT_TEST: galera.galera_pc_ignore_sb
            mysqltest: In included file "./include/galera_wait_ready.inc": 
            included from /usr/share/mysql-test/suite/galera/include/start_mysqld.inc at line 16:
            included from /usr/share/mysql-test/suite/galera/t/galera_pc_ignore_sb.test at line 43:
            At line 28: "Server did not transition to READY state"
             
            The result from queries just before the failure was:
            SET @wsrep_cluster_address_orig = @@GLOBAL.wsrep_cluster_address;
            SET @wsrep_provider_options_orig = @@GLOBAL.wsrep_provider_options;
            SET GLOBAL wsrep_provider_options ='pc.ignore_sb=true';
            Killing server ...
            CREATE TABLE t1 (f1 INTEGER) ENGINE=InnoDB;
            INSERT INTO t1 VALUES (1);
            DROP TABLE t1;
            SELECT VARIABLE_VALUE = 1 FROM INFORMATION_SCHEMA.GLOBAL_STATUS WHERE VARIABLE_NAME = 'wsrep_cluster_size';
            VARIABLE_VALUE = 1
            1
            SELECT VARIABLE_VALUE = 'ON' FROM INFORMATION_SCHEMA.GLOBAL_STATUS WHERE VARIABLE_NAME = 'wsrep_ready';
            VARIABLE_VALUE = 'ON'
            1
            SET GLOBAL wsrep_cluster_address = '';
            SET GLOBAL wsrep_cluster_address = @wsrep_cluster_address_orig;
             
             - saving '/dev/shm/var/4/log/galera.galera_pc_ignore_sb-innodb_plugin/' to '/dev/shm/var/log/galera.galera_pc_ignore_sb-innodb_plugin/'
             
            Retrying test galera.galera_pc_ignore_sb, attempt(2/3)...
            

            Somehow we need to move from split brain situation to normal cluster reliable way. Note that test case does not fail every time only most of the time and more on release builds.

            jplindst Jan Lindström (Inactive) added a comment - After several tries had to give up current version: http://buildbot.askmonty.org/buildbot/builders/kvm-rpm-centos74-amd64/builds/4633/steps/mtr/logs/stdio galera.galera_pc_ignore_sb 'innodb_plugin' w4 [ fail ] Test ended at 2018-10-03 17:31:50   CURRENT_TEST: galera.galera_pc_ignore_sb mysqltest: In included file "./include/galera_wait_ready.inc": included from /usr/share/mysql-test/suite/galera/include/start_mysqld.inc at line 16: included from /usr/share/mysql-test/suite/galera/t/galera_pc_ignore_sb.test at line 43: At line 28: "Server did not transition to READY state"   The result from queries just before the failure was: SET @wsrep_cluster_address_orig = @@GLOBAL.wsrep_cluster_address; SET @wsrep_provider_options_orig = @@GLOBAL.wsrep_provider_options; SET GLOBAL wsrep_provider_options ='pc.ignore_sb=true'; Killing server ... CREATE TABLE t1 (f1 INTEGER) ENGINE=InnoDB; INSERT INTO t1 VALUES (1); DROP TABLE t1; SELECT VARIABLE_VALUE = 1 FROM INFORMATION_SCHEMA.GLOBAL_STATUS WHERE VARIABLE_NAME = 'wsrep_cluster_size'; VARIABLE_VALUE = 1 1 SELECT VARIABLE_VALUE = 'ON' FROM INFORMATION_SCHEMA.GLOBAL_STATUS WHERE VARIABLE_NAME = 'wsrep_ready'; VARIABLE_VALUE = 'ON' 1 SET GLOBAL wsrep_cluster_address = ''; SET GLOBAL wsrep_cluster_address = @wsrep_cluster_address_orig;   - saving '/dev/shm/var/4/log/galera.galera_pc_ignore_sb-innodb_plugin/' to '/dev/shm/var/log/galera.galera_pc_ignore_sb-innodb_plugin/'   Retrying test galera.galera_pc_ignore_sb, attempt(2/3)... Somehow we need to move from split brain situation to normal cluster reliable way. Note that test case does not fail every time only most of the time and more on release builds.
            mkaruza Mario Karuza (Inactive) added a comment - - edited

            Problem is triggered after execution of galera.galera_drop_database test introduced with MDEV-16656. This test should leave cluster in original state before the end of it but it seems that this is not case.
            Problem which is reported here is that after change of 'wsrep_cluster_address' mysqld.1 is not in PRIMARY and will timeout.

            mkaruza Mario Karuza (Inactive) added a comment - - edited Problem is triggered after execution of galera.galera_drop_database test introduced with MDEV-16656 . This test should leave cluster in original state before the end of it but it seems that this is not case. Problem which is reported here is that after change of 'wsrep_cluster_address' mysqld.1 is not in PRIMARY and will timeout.

            People

              jplindst Jan Lindström (Inactive)
              jplindst Jan Lindström (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 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.