mirror of
https://github.com/MariaDB/server.git
synced 2026-05-16 20:07:13 +02:00
832025b512
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.
13 lines
340 B
Text
13 lines
340 B
Text
CREATE TABLE t1 (f1 INTEGER PRIMARY KEY) ENGINE=InnoDB;
|
|
Suspending node_2 ...
|
|
SET SESSION wsrep_sync_wait = 0;
|
|
INSERT INTO t1 VALUES (1);
|
|
Got one of the listed errors
|
|
Resuming node_2 ...
|
|
INSERT INTO t1 VALUES (1);
|
|
SET SESSION wsrep_sync_wait = 0;
|
|
SELECT COUNT(*) = 1 FROM t1;
|
|
COUNT(*) = 1
|
|
1
|
|
SET SESSION wsrep_sync_wait = 15;
|
|
DROP TABLE t1;
|