diff options
| author | Brandon Nesterenko <brandon.nesterenko@mariadb.com> | 2022-05-23 14:14:00 -0600 |
|---|---|---|
| committer | Brandon Nesterenko <brandon.nesterenko@mariadb.com> | 2022-07-26 13:31:27 -0600 |
| commit | 5ab5ff08b008417f32dd4bb15820a1a53ea3821c (patch) | |
| tree | 065fb608faf7067e7efb40e5d2ef1f74d9d7a17e /mysql-test/suite/multi_source/skip_counter.test | |
| parent | 8c2faad576d6a77314e92755a389de2c41e21242 (diff) | |
| download | mariadb-git-5ab5ff08b008417f32dd4bb15820a1a53ea3821c.tar.gz | |
MDEV-19801: Change defaults for CHANGE MASTER TO so that GTID-based replication is used by default if master supports it
This commit makes replicas crash-safe by default by changing the
Using_Gtid value to be Slave_Pos on a fresh slave start and after
RESET SLAVE is issued. If the primary server does not support GTIDs
(i.e., version < 10), the replica will fall back to Using_Gtid=No on
slave start and after RESET SLAVE.
The following additional informational messages/warnings are added:
1. When Using_Gtid is automatically changed. That is, if RESET
SLAVE reverts Using_Gtid back to Slave_Pos, or Using_Gtid is
inferred to No from a CHANGE MASTER TO given with log coordinates
without MASTER_USE_GTID.
2. If options are ignored in CHANGE MASTER TO. If CHANGE MASTER TO
is given with log coordinates, yet also specifies
MASTER_USE_GTID=Slave_Pos, a warning message is given that the log
coordinate options are ignored.
Additionally, an MTR macro has been added for RESET SLAVE,
reset_slave.inc, which provides modes/options for resetting a slave
in log coordinate or gtid modes. When in log coordinates mode, the
macro will execute CHANGE MASTER TO MASTER_USE_GTID=No after the
RESET SLAVE command. When in GTID mode, an extra parameter,
reset_slave_keep_gtid_state, can be set to reset or preserve the
value of gtid_slave_pos.
Reviewed By:
===========
Andrei Elkin <andrei.elkin@mariadb.com>
Diffstat (limited to 'mysql-test/suite/multi_source/skip_counter.test')
| -rw-r--r-- | mysql-test/suite/multi_source/skip_counter.test | 6 |
1 files changed, 4 insertions, 2 deletions
diff --git a/mysql-test/suite/multi_source/skip_counter.test b/mysql-test/suite/multi_source/skip_counter.test index e53d0276a91..e89480f55c5 100644 --- a/mysql-test/suite/multi_source/skip_counter.test +++ b/mysql-test/suite/multi_source/skip_counter.test @@ -38,7 +38,8 @@ create table db.t3 (i int) engine=MyISAM; eval change master 'master1' to master_port=$SERVER_MYPORT_1, master_host='127.0.0.1', -master_user='root'; +master_user='root', +master_use_gtid=no; start slave 'master1'; set default_master_connection = 'master1'; @@ -53,7 +54,8 @@ set default_master_connection = 'master2'; eval change master 'master2' to master_port=$SERVER_MYPORT_2, master_host='127.0.0.1', -master_user='root'; +master_user='root', +master_use_gtid=no; # the schema creation will be replicated from the 1st master, # so we want to skip it in the second replication connection |