Debian Codegraph @

mysql-test/suite/rpl_gtid/r/rpl_gtid_only_no_connection_repo_persistency.result

raw
1 include/master-slave.inc
2 Warnings:
3 Note #### Sending passwords in plain text without SSL/TLS is extremely insecure.
4 Note #### Storing MySQL user name or password information in the connection metadata repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START REPLICA; see the 'START REPLICA Syntax' in the MySQL Manual for more information.
5 [connection master]
6 #
7 # 1. Create a table on the source and replicate it.
8 # Set the value of sync_source_info to 1 so the repo is always synced
9 # Check the repo shows the same value as SHOW REPLICA STATUS
10 [connection slave]
11 SET @@GLOBAL.sync_source_info=1;
12 [connection master]
13 CREATE TABLE t1 (c1 INT NOT NULL PRIMARY KEY);
14 INSERT INTO t1 VALUES (1);
15 include/sync_slave_sql_with_master.inc
16 include/assert.inc [The file position for the repository and the show replica status match]
17 include/assert.inc [The file name for the repository and the show replica status match]
18 #
19 # 2. Stop replication and make the channel use GTID_ONLY=1
20 # Start replication and add some values to the table.
21 # Check the repo shows the old values in relation to SHOW REPLICA STATUS
22 include/stop_slave.inc
23 CHANGE REPLICATION SOURCE TO GTID_ONLY = 1, REQUIRE_ROW_FORMAT=1;
24 include/start_slave.inc
25 [connection master]
26 INSERT INTO t1 VALUES (2);
27 include/sync_slave_sql_with_master.inc
28 include/assert.inc [The repository position is not the one shown on show replica status]
29 include/assert.inc [The repository pos value is still the same]
30 include/assert.inc [The repository name value is still the same]
31 #
32 # 3. Stop replication
33 # Check the repo still shows the old values in relation to SHOW REPLICA STATUS
34 include/stop_slave.inc
35 include/assert.inc [The repository position is not the one shown on show replica status]
36 include/assert.inc [The repository pos value is still the same]
37 include/assert.inc [The repository name value is still the same]
38 #
39 # 4. Start replication again
40 # Check the repo still shows the old values in relation to SHOW REPLICA STATUS
41 include/start_slave.inc
42 [connection master]
43 FLUSH LOGS;
44 INSERT INTO t1 VALUES (3);
45 include/sync_slave_sql_with_master.inc
46 include/assert.inc [The repository position is not the one shown on show replica status]
47 include/assert.inc [The repository file name is not the one shown on show replica status]
48 include/assert.inc [The repository pos value is still the same]
49 include/assert.inc [The repository name value is still the same]
50 #
51 # 5. Kill the IO thread
52 # Check the repo still shows the old values in relation to SHOW REPLICA STATUS
53 include/wait_for_slave_io_to_stop.inc
54 include/assert.inc [The repository position is not the one shown on show replica status]
55 include/assert.inc [The repository file name is not the one shown on show replica status]
56 include/assert.inc [The repository pos value is still the same]
57 include/assert.inc [The repository name value is still the same]
58 #
59 # 6. Change a replication connection setting with CHANGE REPLICATION SOURCE
60 # Check the repo now has the same value in relation to SHOW REPLICA STATUS
61 include/stop_slave.inc
62 CHANGE REPLICATION SOURCE TO SOURCE_CONNECT_RETRY = 10000;
63 include/assert.inc [The repository now has the lastest position]
64 include/assert.inc [The file name for the repository and the show replica status match]
65 #
66 # 7. Restart the replica server
67 # Check the repo still shows the old values
68 include/start_slave.inc
69 [connection master]
70 INSERT INTO t1 VALUES (4);
71 include/sync_slave_sql_with_master.inc
72 include/assert.inc [The repository position is not the one shown on show replica status]
73 include/rpl_restart_server.inc [server_number=2 parameters: --skip_replica_start=FALSE]
74 include/assert.inc [The repository pos value is still the same]
75 #
76 # 8. Add some values and check the repo is again stale
77 # Execute a RESET REPLICA command
78 # Check the repo persisted the reset position
79 [connection master]
80 INSERT INTO t1 VALUES (5);
81 include/sync_slave_sql_with_master.inc
82 include/assert.inc [The repository has not persisted]
83 include/stop_slave.inc
84 RESET REPLICA;
85 include/assert.inc [The repository has the reset position]
86 include/assert.inc [The repository has the reset position]
87 #
88 # 9. Check RESET REPLICA ALL removes all the information
89 include/start_slave.inc
90 [connection master]
91 INSERT INTO t1 VALUES (6);
92 include/sync_slave_sql_with_master.inc
93 include/assert.inc [The repository still has the reset position]
94 include/stop_slave.inc
95 RESET REPLICA ALL;
96 include/assert.inc [The repository info was deleted]
97 #
98 # 10. Cleanup
99 CHANGE REPLICATION SOURCE TO SOURCE_HOST='127.0.0.1', SOURCE_PORT=MASTER_PORT, SOURCE_USER='root';
100 Warnings:
101 Note 1759 Sending passwords in plain text without SSL/TLS is extremely insecure.
102 Note 1760 Storing MySQL user name or password information in the connection metadata repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START REPLICA; see the 'START REPLICA Syntax' in the MySQL Manual for more information.
103 include/start_slave.inc
104 SET @@GLOBAL.sync_source_info=SYNC_SOURCE_VAL;
105 [connection master]
106 DROP TABLE t1;
107 include/rpl_end.inc