mariadb/mysql-test/suite/galera/r/galera_gtid_trx_conflict.result
mkaruza 53173709b3 MDEV-26223 Galera cluster node consider old server_id value even after modification of server_id [wsrep_gtid_mode=ON]
Variable `wsrep_new_cluster` now will be TRUE also when there is only `gcomm://` used
in configuration. This configuration, even without --wsrep-new-cluster,
is considered to bootstrap new cluster.

Updated galera GTID test to ignore warning message when non bootstrap
node have server-id different thant one cluster is initialized with.

Reviewed-by: Jan Lindström <jan.lindstrom@mariadb.com>
2022-01-27 08:22:46 +02:00

45 lines
1.1 KiB
Text

connection node_2;
connection node_1;
CREATE TABLE t1 (f1 INTEGER PRIMARY KEY) ENGINE=InnoDB;
connection node_1;
SET AUTOCOMMIT = OFF;
START TRANSACTION;
INSERT INTO t1 VALUES(1);
connection node_2;
SET AUTOCOMMIT = OFF;
SET @@wsrep_gtid_seq_no = 100;
START TRANSACTION;
INSERT INTO t1 VALUES(1);
connection node_1;
COMMIT;
connect node_2a, 127.0.0.1, root, , test, $NODE_MYPORT_2;
connection node_2a;
connection node_2;
COMMIT;
ERROR 40001: Deadlock found when trying to get lock; try restarting transaction
# Expected GTID value 1-1-2 on both nodes
SELECT @@gtid_binlog_state;
@@gtid_binlog_state
1-1-2
SET AUTOCOMMIT = ON;
INSERT INTO t1 VALUES(2);
# Expected GTID value 1-1-100 on both nodes, seqno is set with wsrep_gtid_seq_no
SELECT @@gtid_binlog_state;
@@gtid_binlog_state
1-1-100
connection node_1;
SELECT @@gtid_binlog_state;
@@gtid_binlog_state
1-1-100
SET AUTOCOMMIT = ON;
INSERT INTO t1 VALUES(3);
# Expected GTID value 1-1-101 on both nodes
SELECT @@gtid_binlog_state;
@@gtid_binlog_state
1-1-101
connection node_2;
SELECT @@gtid_binlog_state;
@@gtid_binlog_state
1-1-101
DROP TABLE t1;
CALL mtr.add_suppression("Ignoring server id for non bootstrap node");