Debian Codegraph @

mysql-test/suite/group_replication/r/gr_acf_receiver_primary_change.result

raw
1 include/group_replication.inc [rpl_server_count=4]
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 server1]
6
7 # 1. Create a replication channel to replicate from server4 to
8 # to server1 on both server1 and 2.
9
10 CHANGE REPLICATION SOURCE TO SOURCE_HOST='127.0.0.1', SOURCE_USER='root', SOURCE_AUTO_POSITION=1, SOURCE_PORT=SERVER_4_PORT, SOURCE_CONNECT_RETRY=1, SOURCE_RETRY_COUNT=1, SOURCE_CONNECTION_AUTO_FAILOVER=1 FOR CHANNEL 'ch1';
11 Warnings:
12 Note 1759 Sending passwords in plain text without SSL/TLS is extremely insecure.
13 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.
14 [connection server2]
15 CHANGE REPLICATION SOURCE TO SOURCE_HOST='127.0.0.1', SOURCE_USER='root', SOURCE_AUTO_POSITION=1, SOURCE_PORT=SERVER_4_PORT, SOURCE_CONNECT_RETRY=1, SOURCE_RETRY_COUNT=1, SOURCE_CONNECTION_AUTO_FAILOVER=1 FOR CHANNEL 'ch1';
16 Warnings:
17 Note 1759 Sending passwords in plain text without SSL/TLS is extremely insecure.
18 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.
19
20 # 2. Deploy a 2 members receiver group in single primary mode.
21
22 [connection server1]
23 include/start_and_bootstrap_group_replication.inc
24 include/wait_for_slave_to_start.inc [FOR CHANNEL 'ch1']
25 include/assert.inc [Verify replica_monitor thread is running]
26 [connection server2]
27 include/start_group_replication.inc
28 #
29 # 3. Deploy a 2 members sender group in single primary mode.
30 #
31 [connection server3]
32 include/start_and_bootstrap_group_replication.inc
33 [connection server4]
34 include/start_group_replication.inc
35
36 # 4. Add replication connection details of managed channel ch1
37 # to replication_asynchronous_connection_failover_managed table
38 # through asynchronous_connection_failover_add_managed() UDF.
39
40 [connection server1]
41 SELECT asynchronous_connection_failover_add_managed('ch1', 'GroupReplication', "GROUP_NAME_SERVER2",'127.0.0.1', SERVER_MYPORT_4, '', 80, 60);
42 asynchronous_connection_failover_add_managed('ch1', 'GroupReplication', "GROUP_NAME_SERVER2",'127.0.0.1', SERVER_MYPORT_4, '', 80, 60)
43 The UDF asynchronous_connection_failover_add_managed() executed successfully.
44
45 # 5. Verify replication_asynchronous_connection_failover on
46 # server1 has two rows and member action configuration version
47 # value for replication_asynchronous_connection_failover
48 # and for replication_asynchronous_connection_failover_managed.
49
50
51 # 6. Verify replication_asynchronous_connection_failover on
52 # server2 has two rows and member action configuration version
53 # value for replication_asynchronous_connection_failover
54 # and for replication_asynchronous_connection_failover_managed.
55
56 [connection server2]
57
58 # 7. Stop group replication on existing primary (server1), and change
59 # primary to server2. The asynchronous replication channel (ch1)
60 # connection will be started without any error.
61
62 [connection server1]
63 include/stop_slave.inc [FOR CHANNEL 'ch1']
64 [connection server2]
65 SELECT group_replication_set_as_primary("SERVER2_UUID");
66 group_replication_set_as_primary("SERVER2_UUID")
67 Primary server switched to: SERVER2_UUID
68 include/gr_wait_primary_member_uuid.inc
69 include/wait_for_slave_to_start.inc [FOR CHANNEL 'ch1']
70 include/assert.inc [Verify replica_monitor thread is running]
71
72 # 8. Delete replication connection details for managed channel ch1
73 # from replication_asynchronous_connection_failover_managed
74 # and replication_asynchronous_connection_failover table
75 # through asynchronous_connection_failover_delete_managed() UDF.
76
77 [connection server2]
78 SELECT asynchronous_connection_failover_delete_managed('ch1', 'GROUP_NAME_SERVER2');
79 asynchronous_connection_failover_delete_managed('ch1', 'GROUP_NAME_SERVER2')
80 The UDF asynchronous_connection_failover_delete_managed() executed successfully.
81
82 # 9. Verify replication_asynchronous_connection_failover on
83 # server2 is empty and member action configuration version
84 # value for replication_asynchronous_connection_failover
85 # and for replication_asynchronous_connection_failover_managed.
86
87 [connection server2]
88
89 # 10. Verify replication_asynchronous_connection_failover on
90 # server1 is empty and member action configuration version
91 # value for replication_asynchronous_connection_failover
92 # and for replication_asynchronous_connection_failover_managed.
93
94 [connection server1]
95 #
96 # 11. Clean up.
97 #
98 [connection server1]
99 include/rpl_reset_slave.inc
100 [connection server2]
101 include/stop_slave.inc [FOR CHANNEL 'ch1']
102 include/rpl_reset_slave.inc
103 [connection server4]
104 include/stop_group_replication.inc
105 [connection server3]
106 include/stop_group_replication.inc
107 [connection server2]
108 include/stop_group_replication.inc
109 [connection server1]
110 include/stop_group_replication.inc
111 include/group_replication_end.inc