1. 28 Mar, 2018 2 commits
    • Daniele Sciascia's avatar
      MDEV-13549 Fix and re-enable MTR test galera.galera_gtid_slave · e3761224
      Daniele Sciascia authored
      This patch makes two changes:
      
      * It replaces `--sleep 1` with appropriate wait_conditions, and
        removes another `--sleep 1` which is no longer necessary, after
        MDEV-14144 has been fixed.
      
      * It moves the `RESET MASTER` from node_1 at the very end, when it
        it sure that the other nodes have applied the the final cleanup
        `DROP TABLE t1,t2.`
        This solves the problem with the `DROP TABLE` not being replicated
        to the asynchronous slaves, which would make the test fail with:
        `Timeout in wait_condition.inc for SELECT COUNT(*) = 0 FROM INFORMATION_SCHEMA.TABLES WHERE TABLE_NAME = 't1';`
      e3761224
    • Jan Lindström's avatar
      Merge pull request #673 from codership/MDEV-13549-fixes-for-galera_suspend_slave · 11ac2df0
      Jan Lindström authored
      MDEV-13549 Fix and re-enable test galera.galera_suspend_slave
      11ac2df0
  2. 27 Mar, 2018 2 commits
    • Daniel Bartholomew's avatar
      bump the VERSION · db16ae54
      Daniel Bartholomew authored
      db16ae54
    • Daniele Sciascia's avatar
      MDEV-13549 Fix and re-enable test galera.galera_suspend_slave · 832025b5
      Daniele Sciascia authored
      Test galera_suspend_slave checks that after suspending a galera
      node, like this:
      ```
      --perl
              my $pid_filename = $ENV{'NODE_2_PIDFILE'};
              my $mysqld_pid = `cat $pid_filename`;
              chomp($mysqld_pid);
              system("kill -SIGSTOP $mysqld_pid");
              exit(0);
      EOF
      ```
      
      the remaining one node cluster is no longer able to successfully
      INSERT new rows:
      ```
      --error ER_UNKNOWN_COM_ERROR,ER_LOCK_WAIT_TIMEOUT,ER_LOCK_DEADLOCK,ER_ERROR_DURING_COMMIT
      INSERT INTO t1 VALUES (1);
      ```
      
      On rare occasions when the system is overloaded, it appears that
      suspending the process with ```system("kill -SIGSTOP $mysqld_pid")```
      takes some time, enough for the subsequent INSERT to succeed. In which
      case the test fails because it rightly expects the INSERT to fail.
      
      To fix the problem, the patch makes sure that the cluster has shrinked
      to one node, before trying to INSERT the new value.
      832025b5
  3. 26 Mar, 2018 5 commits
  4. 24 Mar, 2018 3 commits
  5. 23 Mar, 2018 7 commits
  6. 22 Mar, 2018 14 commits
  7. 21 Mar, 2018 7 commits