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

rpl.rpl_semi_sync failed in buildbot, result mismatch, Rpl_semi_sync_master_status on/off

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Duplicate
    • 5.5(EOL), 10.0(EOL), 10.1(EOL), 10.2(EOL), 10.3(EOL), 10.4(EOL), 10.5
    • N/A
    • Tests
    • None
    • 5.5.59

    Description

      http://buildbot.askmonty.org/buildbot/builders/kvm-deb-precise-amd64/builds/7081/steps/test_5/logs/stdio

      rpl.rpl_semi_sync 'row,xtradb'           w4 [ fail ]
      		 
              Test ended at 2016-09-28 02:31:10
      		 
       
      		 
      CURRENT_TEST: rpl.rpl_semi_sync
      		 
      --- /usr/share/mysql/mysql-test/suite/rpl/r/rpl_semi_sync.result	2016-09-27 18:47:12.000000000 +0300
      		 
      +++ /run/shm/var/4/log/rpl_semi_sync.reject	2016-09-28 02:31:09.703012788 +0300
      		 
      @@ -227,7 +227,7 @@
      		 
       [ master status should be ON again after slave catches up ]
      		 
       show status like 'Rpl_semi_sync_master_status';
      		 
       Variable_name	Value
      		 
      -Rpl_semi_sync_master_status	ON
      		 
      +Rpl_semi_sync_master_status	OFF
      		 
       show status like 'Rpl_semi_sync_master_no_tx';
      		 
       Variable_name	Value
      		 
       Rpl_semi_sync_master_no_tx	12
      		 
      @@ -249,10 +249,10 @@
      		 
       [ Semi-sync master status variables before FLUSH STATUS ]
      		 
       SHOW STATUS LIKE 'Rpl_semi_sync_master_no_tx';
      		 
       Variable_name	Value
      		 
      -Rpl_semi_sync_master_no_tx	12
      		 
      +Rpl_semi_sync_master_no_tx	13
      		 
       SHOW STATUS LIKE 'Rpl_semi_sync_master_yes_tx';
      		 
       Variable_name	Value
      		 
      -Rpl_semi_sync_master_yes_tx	15
      		 
      +Rpl_semi_sync_master_yes_tx	14
      		 
       FLUSH NO_WRITE_TO_BINLOG STATUS;
      		 
       [ Semi-sync master status variables after FLUSH STATUS ]
      		 
       SHOW STATUS LIKE 'Rpl_semi_sync_master_no_tx';
      		 
       
      		 
      mysqltest: Result length mismatch

      Attachments

        Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. MDEV-22008 rpl.rpl_semi_sync fails with wrong value for Rpl_semi_sync_master_clients

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed
          relates to

          Task - A task that needs to be done. MDEV-7069 Fix buildbot failures in main server trees

          • Major - Major loss of function.
          • Stalled

          Bug - A problem which impairs or prevents the functions of the product. MDEV-14366 rpl.rpl_semi_sync_after_sync, rpl.rpl_semi_sync_after_sync_row failed in buildbot with wrong result

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            elenst Elena Stepanova added a comment -

            A different flavor on 10.0:
            http://buildbot.askmonty.org/buildbot/builders/kvm-bintar-centos5-x86/builds/6234/steps/test/logs/stdio

            rpl.rpl_semi_sync 'innodb_plugin,row'    w3 [ fail ]
            		 
                    Test ended at 2017-01-22 05:30:22
            		 
             
            		 
            CURRENT_TEST: rpl.rpl_semi_sync
            		 
            --- /usr/local/mariadb-10.0.30-linux-i686/mysql-test/suite/rpl/r/rpl_semi_sync.result	2017-01-22 04:46:12.000000000 +0100
            		 
            +++ /usr/local/mariadb-10.0.30-linux-i686/mysql-test/suite/rpl/r/rpl_semi_sync.reject	2017-01-22 05:30:22.000000000 +0100
            		 
            @@ -91,9 +91,9 @@
            		 
             show status like 'Rpl_semi_sync_master_yes_tx';
            		 
             Variable_name	Value
            		 
             Rpl_semi_sync_master_yes_tx	1
            		 
            -select CONNECTIONS_NORMAL_SLAVE - CONNECTIONS_NORMAL_SLAVE as 'Should be 0';
            		 
            +select CONNECTIONS_SEMISYNC_SLAVE - CONNECTIONS_NORMAL_SLAVE as 'Should be 0';
            		 
             Should be 0
            		 
            -0
            		 
            +1
            		 
             [ insert records to table ]
            		 
             insert t1 values (10);
            		 
             insert t1 values (9);
            		 
             
            		 
            mysqltest: Result length mismatch

            elenst Elena Stepanova added a comment - A different flavor on 10.0: http://buildbot.askmonty.org/buildbot/builders/kvm-bintar-centos5-x86/builds/6234/steps/test/logs/stdio rpl.rpl_semi_sync 'innodb_plugin,row' w3 [ fail ] Test ended at 2017-01-22 05:30:22   CURRENT_TEST: rpl.rpl_semi_sync --- /usr/local/mariadb-10.0.30-linux-i686/mysql-test/suite/rpl/r/rpl_semi_sync.result 2017-01-22 04:46:12.000000000 +0100 +++ /usr/local/mariadb-10.0.30-linux-i686/mysql-test/suite/rpl/r/rpl_semi_sync.reject 2017-01-22 05:30:22.000000000 +0100 @@ -91,9 +91,9 @@ show status like 'Rpl_semi_sync_master_yes_tx'; Variable_name Value Rpl_semi_sync_master_yes_tx 1 -select CONNECTIONS_NORMAL_SLAVE - CONNECTIONS_NORMAL_SLAVE as 'Should be 0'; +select CONNECTIONS_SEMISYNC_SLAVE - CONNECTIONS_NORMAL_SLAVE as 'Should be 0'; Should be 0 -0 +1 [ insert records to table ] insert t1 values (10); insert t1 values (9);   mysqltest: Result length mismatch
            elenst Elena Stepanova added a comment -

            binlog_encryption.rpl_semi_sync inherited the failure of the first kind:
            http://askmonty.org/buildbot/builders/kvm-bintar-centos5-amd64/builds/4770

            binlog_encryption.rpl_semi_sync 'mix,xtradb' w2 [ fail ]
            		 
                    Test ended at 2017-03-07 18:44:40
            		 
             
            		 
            CURRENT_TEST: binlog_encryption.rpl_semi_sync
            		 
            --- /usr/local/mariadb-10.1.22-linux-x86_64/mysql-test/suite/binlog_encryption/rpl_semi_sync.result	2017-03-07 14:53:52.000000000 +0100
            		 
            +++ /usr/local/mariadb-10.1.22-linux-x86_64/mysql-test/suite/binlog_encryption/rpl_semi_sync.reject	2017-03-07 18:44:39.000000000 +0100
            		 
            @@ -227,7 +227,7 @@
            		 
             [ master status should be ON again after slave catches up ]
            		 
             show status like 'Rpl_semi_sync_master_status';
            		 
             Variable_name	Value
            		 
            -Rpl_semi_sync_master_status	ON
            		 
            +Rpl_semi_sync_master_status	OFF
            		 
             show status like 'Rpl_semi_sync_master_no_tx';
            		 
             Variable_name	Value
            		 
             Rpl_semi_sync_master_no_tx	12
            		 
            @@ -249,10 +249,10 @@
            		 
             [ Semi-sync master status variables before FLUSH STATUS ]
            		 
             SHOW STATUS LIKE 'Rpl_semi_sync_master_no_tx';
            		 
             Variable_name	Value
            		 
            -Rpl_semi_sync_master_no_tx	12
            		 
            +Rpl_semi_sync_master_no_tx	13
            		 
             SHOW STATUS LIKE 'Rpl_semi_sync_master_yes_tx';
            		 
             Variable_name	Value
            		 
            -Rpl_semi_sync_master_yes_tx	15
            		 
            +Rpl_semi_sync_master_yes_tx	14
            		 
             FLUSH NO_WRITE_TO_BINLOG STATUS;
            		 
             [ Semi-sync master status variables after FLUSH STATUS ]
            		 
             SHOW STATUS LIKE 'Rpl_semi_sync_master_no_tx';
            		 
             
            		 
            mysqltest: Result length mismatch

            elenst Elena Stepanova added a comment - binlog_encryption.rpl_semi_sync inherited the failure of the first kind: http://askmonty.org/buildbot/builders/kvm-bintar-centos5-amd64/builds/4770 binlog_encryption.rpl_semi_sync 'mix,xtradb' w2 [ fail ] Test ended at 2017-03-07 18:44:40   CURRENT_TEST: binlog_encryption.rpl_semi_sync --- /usr/local/mariadb-10.1.22-linux-x86_64/mysql-test/suite/binlog_encryption/rpl_semi_sync.result 2017-03-07 14:53:52.000000000 +0100 +++ /usr/local/mariadb-10.1.22-linux-x86_64/mysql-test/suite/binlog_encryption/rpl_semi_sync.reject 2017-03-07 18:44:39.000000000 +0100 @@ -227,7 +227,7 @@ [ master status should be ON again after slave catches up ] show status like 'Rpl_semi_sync_master_status'; Variable_name Value -Rpl_semi_sync_master_status ON +Rpl_semi_sync_master_status OFF show status like 'Rpl_semi_sync_master_no_tx'; Variable_name Value Rpl_semi_sync_master_no_tx 12 @@ -249,10 +249,10 @@ [ Semi-sync master status variables before FLUSH STATUS ] SHOW STATUS LIKE 'Rpl_semi_sync_master_no_tx'; Variable_name Value -Rpl_semi_sync_master_no_tx 12 +Rpl_semi_sync_master_no_tx 13 SHOW STATUS LIKE 'Rpl_semi_sync_master_yes_tx'; Variable_name Value -Rpl_semi_sync_master_yes_tx 15 +Rpl_semi_sync_master_yes_tx 14 FLUSH NO_WRITE_TO_BINLOG STATUS; [ Semi-sync master status variables after FLUSH STATUS ] SHOW STATUS LIKE 'Rpl_semi_sync_master_no_tx';   mysqltest: Result length mismatch
            alice Alice Sherepa added a comment -

            also on 10.2 http://buildbot.askmonty.org/buildbot/builders/kvm-bintar-trusty-amd64/builds/3549/steps/test/logs/stdio

            binlog_encryption.rpl_semi_sync 'innodb,row' w2 [ fail ]
            		 
                    Test ended at 2017-11-16 18:12:37
            		 
             
            		 
            CURRENT_TEST: binlog_encryption.rpl_semi_sync
            		 
            --- /usr/local/mariadb-10.2.11-linux-x86_64/mysql-test/suite/binlog_encryption/rpl_semi_sync.result	2017-11-16 16:33:24.000000000 +0000
            		 
            +++ /usr/local/mariadb-10.2.11-linux-x86_64/mysql-test/suite/binlog_encryption/rpl_semi_sync.reject	2017-11-16 18:12:37.079967643 +0000
            		 
            @@ -236,7 +236,7 @@
            		 
             [ master status should be ON again after slave catches up ]
            		 
             show status like 'Rpl_semi_sync_master_status';
            		 
             Variable_name	Value
            		 
            -Rpl_semi_sync_master_status	ON
            		 
            +Rpl_semi_sync_master_status	OFF
            		 
             show status like 'Rpl_semi_sync_master_no_tx';
            		 
             Variable_name	Value
            		 
             Rpl_semi_sync_master_no_tx	12
            		 
             
            		 
            mysqltest: Result length mismatch

            alice Alice Sherepa added a comment - also on 10.2 http://buildbot.askmonty.org/buildbot/builders/kvm-bintar-trusty-amd64/builds/3549/steps/test/logs/stdio binlog_encryption.rpl_semi_sync 'innodb,row' w2 [ fail ] Test ended at 2017-11-16 18:12:37   CURRENT_TEST: binlog_encryption.rpl_semi_sync --- /usr/local/mariadb-10.2.11-linux-x86_64/mysql-test/suite/binlog_encryption/rpl_semi_sync.result 2017-11-16 16:33:24.000000000 +0000 +++ /usr/local/mariadb-10.2.11-linux-x86_64/mysql-test/suite/binlog_encryption/rpl_semi_sync.reject 2017-11-16 18:12:37.079967643 +0000 @@ -236,7 +236,7 @@ [ master status should be ON again after slave catches up ] show status like 'Rpl_semi_sync_master_status'; Variable_name Value -Rpl_semi_sync_master_status ON +Rpl_semi_sync_master_status OFF show status like 'Rpl_semi_sync_master_no_tx'; Variable_name Value Rpl_semi_sync_master_no_tx 12   mysqltest: Result length mismatch
            alice Alice Sherepa added a comment -

            and 5.5 is also affected http://buildbot.askmonty.org/buildbot/builders/kvm-deb-trusty-x86/builds/5021/steps/mtr/logs/stdio

            rpl.rpl_semi_sync 'innodb_plugin,mix'    w4 [ fail ]
            		 
                    Test ended at 2017-11-30 10:22:39
            		 
             
            		 
            CURRENT_TEST: rpl.rpl_semi_sync
            		 
            --- /usr/share/mysql/mysql-test/suite/rpl/r/rpl_semi_sync.result	2017-11-30 09:59:47.000000000 +0000
            		 
            +++ /run/shm/var/4/log/rpl_semi_sync.reject	2017-11-30 10:22:39.700809602 +0000
            		 
            @@ -196,7 +196,7 @@
            		 
             [ master status should be ON again after slave catches up ]
            		 
             show status like 'Rpl_semi_sync_master_status';
            		 
             Variable_name	Value
            		 
            -Rpl_semi_sync_master_status	ON
            		 
            +Rpl_semi_sync_master_status	OFF
            		 
             show status like 'Rpl_semi_sync_master_no_tx';
            		 
             Variable_name	Value
            		 
             Rpl_semi_sync_master_no_tx	12
            		 
             
            		 
            mysqltest: Result length mismatch
            		 
             
            		 
             - saving '/run/shm/var/4/log/rpl.rpl_semi_sync-innodb_plugin,mix/' to '/run/shm/var/log/rpl.rpl_semi_sync-innodb_plugin,mix/'
            		 
             
            		 
            Retrying test rpl.rpl_semi_sync, attempt(2/3)...
            		 
             
            		 
            worker[4] > Restart  - not started
            		 
            worker[4] > Restart  - not started
            		 
            ***Warnings generated in error logs during shutdown after running tests: rpl.rpl_semi_sync
            		 
             
            		 
            171130 10:22:34 [Warning] Timeout waiting for reply of binlog (file: master-bin.000001, pos: 345), semi-sync up to file , position 0.
            		 
            171130 10:22:34 [ERROR] Read semi-sync reply network error:  (errno: 1158)
            		 
            171130 10:22:39 [Warning] Timeout waiting for reply of binlog (file: master-bin.000001, pos: 3204), semi-sync up to file master-bin.000001, position 3019.
            		 
            171130 10:22:39 [Warning] Master server does not support semi-sync, fallback to asynchronous replication

            alice Alice Sherepa added a comment - and 5.5 is also affected http://buildbot.askmonty.org/buildbot/builders/kvm-deb-trusty-x86/builds/5021/steps/mtr/logs/stdio rpl.rpl_semi_sync 'innodb_plugin,mix' w4 [ fail ] Test ended at 2017-11-30 10:22:39   CURRENT_TEST: rpl.rpl_semi_sync --- /usr/share/mysql/mysql-test/suite/rpl/r/rpl_semi_sync.result 2017-11-30 09:59:47.000000000 +0000 +++ /run/shm/var/4/log/rpl_semi_sync.reject 2017-11-30 10:22:39.700809602 +0000 @@ -196,7 +196,7 @@ [ master status should be ON again after slave catches up ] show status like 'Rpl_semi_sync_master_status'; Variable_name Value -Rpl_semi_sync_master_status ON +Rpl_semi_sync_master_status OFF show status like 'Rpl_semi_sync_master_no_tx'; Variable_name Value Rpl_semi_sync_master_no_tx 12   mysqltest: Result length mismatch   - saving '/run/shm/var/4/log/rpl.rpl_semi_sync-innodb_plugin,mix/' to '/run/shm/var/log/rpl.rpl_semi_sync-innodb_plugin,mix/'   Retrying test rpl.rpl_semi_sync, attempt(2/3)...   worker[4] > Restart - not started worker[4] > Restart - not started ***Warnings generated in error logs during shutdown after running tests: rpl.rpl_semi_sync   171130 10:22:34 [Warning] Timeout waiting for reply of binlog (file: master-bin.000001, pos: 345), semi-sync up to file , position 0. 171130 10:22:34 [ERROR] Read semi-sync reply network error: (errno: 1158) 171130 10:22:39 [Warning] Timeout waiting for reply of binlog (file: master-bin.000001, pos: 3204), semi-sync up to file master-bin.000001, position 3019. 171130 10:22:39 [Warning] Master server does not support semi-sync, fallback to asynchronous replication
            alice Alice Sherepa added a comment -

            the same on 10.4,10.5:
            http://buildbot.askmonty.org/buildbot/builders/kvm-bintar-quantal-x86/builds/23526/steps/mtr/logs/stdio
            http://buildbot.askmonty.org/buildbot/builders/kvm-bintar-centos6-x86/builds/1295/steps/mtr/logs/stdio

            alice Alice Sherepa added a comment - the same on 10.4,10.5: http://buildbot.askmonty.org/buildbot/builders/kvm-bintar-quantal-x86/builds/23526/steps/mtr/logs/stdio http://buildbot.askmonty.org/buildbot/builders/kvm-bintar-centos6-x86/builds/1295/steps/mtr/logs/stdio

            People

              Elkin Andrei Elkin
              elenst Elena Stepanova
              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.