Debian Codegraph @

mysql-test/suite/group_replication/r/gr_acf_receiver_on_spm.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 [connection server2]
7 SET SESSION sql_log_bin = 0;
8 call mtr.add_suppression("Can't start replica IO THREAD of channel 'ch1' when group replication is running with single-primary mode on a secondary member.");
9 call mtr.add_suppression("Can't start replica SQL THREAD of channel 'ch1' when group replication is running with single-primary mode on a secondary member.");
10 call mtr.add_suppression("Run function 'thread_start' in plugin 'group_replication' failed");
11 call mtr.add_suppression("Run function 'applier_start' in plugin 'group_replication' failed");
12 call mtr.add_suppression("Failed to run 'thread_start' hook");
13 call mtr.add_suppression("Failed to run 'applier_start' hook");
14 SET SESSION sql_log_bin = 1;
15
16 # 1. Create a replication channel to replicate from server4 to
17 # to server1 on both server1 and 2.
18
19 [connection server1]
20 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';
21 Warnings:
22 Note 1759 Sending passwords in plain text without SSL/TLS is extremely insecure.
23 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.
24 [connection server2]
25 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';
26 Warnings:
27 Note 1759 Sending passwords in plain text without SSL/TLS is extremely insecure.
28 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.
29
30 # 2. Add server4 using asynchronous_connection_failover_add_managed
31 # UDF on stand alone server2.
32 # It will be allowed but the configuration will not be propagated.
33
34 [connection server2]
35 SELECT asynchronous_connection_failover_add_managed('ch1', 'GroupReplication', 'GROUP_NAME_SERVER1', '127.0.0.1', SERVER_MYPORT_4, '', 90, 70);;
36 asynchronous_connection_failover_add_managed('ch1', 'GroupReplication', 'GROUP_NAME_SERVER1', '127.0.0.1', SERVER_MYPORT_4, '', 90, 70)
37 The UDF asynchronous_connection_failover_add_managed() executed successfully.
38 include/assert.inc ['There is one row in performance_schema.replication_asynchronous_connection_failover']
39 include/assert.inc ['The version of replication_asynchronous_connection_failover must be 1']
40 include/assert.inc ['There is one row in performance_schema.replication_asynchronous_connection_failover_managed']
41 include/assert.inc ['The version of replication_asynchronous_connection_failover_managed must be 1']
42 [connection server1]
43 include/assert.inc ['There are no rows in performance_schema.replication_asynchronous_connection_failover']
44 include/assert.inc ['There is no version of replication_asynchronous_connection_failover']
45 include/assert.inc ['There are no rows in performance_schema.replication_asynchronous_connection_failover_managed']
46 include/assert.inc ['There is no version of replication_asynchronous_connection_failover_managed']
47
48 # 3. Deploy a 2 members receiver group in single primary mode.
49 # Since server1 will bootstrap the group, server1 configuration will
50 # be the group configuration, which will override server2
51 # configuration when server2 joins the group.
52
53 [connection server1]
54 include/start_and_bootstrap_group_replication.inc
55 include/assert.inc ['The performance_schema.replication_asynchronous_connection_failover table is empty']
56 include/assert.inc ['The version of replication_asynchronous_connection_failover must be 0']
57 include/assert.inc ['The performance_schema.replication_asynchronous_connection_failover_managed table is empty']
58 include/assert.inc ['The version of replication_asynchronous_connection_failover_managed must be 0']
59 [connection server2]
60 include/start_group_replication.inc
61 include/assert.inc ['The performance_schema.replication_asynchronous_connection_failover table is empty']
62 include/assert.inc ['The version of replication_asynchronous_connection_failover must be 0']
63 include/assert.inc ['The performance_schema.replication_asynchronous_connection_failover_managed table is empty']
64 include/assert.inc ['The version of replication_asynchronous_connection_failover_managed must be 0']
65
66 # 4. Error adding managed group to secondary server2.
67
68 SELECT asynchronous_connection_failover_add_managed('ch1', 'GroupReplication', 'GROUP_A', '127.0.0.1', SERVER_MYPORT_5, '', 90, 70);;
69 ERROR HY000: Can't initialize function 'asynchronous_connection_failover_add_managed'; Can't execute the given operation on a Group Replication secondary member.
70 SELECT asynchronous_connection_failover_add_source('ch1', '127.0.0.1', SERVER_MYPORT_5, '', 50);
71 ERROR HY000: Can't initialize function 'asynchronous_connection_failover_add_source'; Can't execute the given operation on a Group Replication secondary member.
72 include/assert.inc ['There are no rows in performance_schema.replication_asynchronous_connection_failover']
73 include/assert.inc ['There is no version of replication_asynchronous_connection_failover']
74 include/assert.inc ['There are no rows in performance_schema.replication_asynchronous_connection_failover_managed']
75 include/assert.inc ['There is no version of replication_asynchronous_connection_failover_managed']
76 #
77 # 5. Deploy a 2 members sender group in single primary mode.
78 #
79 [connection server3]
80 include/start_and_bootstrap_group_replication.inc
81 [connection server4]
82 include/start_group_replication.inc
83
84 # 6. Error starting a replication channel on secondary member server2.
85
86 [connection server2]
87 START REPLICA FOR CHANNEL 'ch1';
88 include/wait_for_slave_sql_error.inc [errno=13117 FOR CHANNEL 'ch1']
89 include/assert_grep.inc [Server executed GTID set is logged.]
90 include/assert_grep.inc [Server executed GTID set is logged.]
91 STOP REPLICA FOR CHANNEL 'ch1';
92 Warnings:
93 Note 3084 Replication thread(s) for channel 'ch1' are already stopped.
94
95 # 7. Add replication connection details of managed channel ch1
96 # to replication_asynchronous_connection_failover_managed table
97 # through asynchronous_connection_failover_add_managed() UDF.
98
99 [connection server1]
100 SELECT asynchronous_connection_failover_add_managed('ch1', 'GroupReplication', "GROUP_NAME_SERVER2",'127.0.0.1', SERVER_MYPORT_4, '', 80, 60);
101 asynchronous_connection_failover_add_managed('ch1', 'GroupReplication', "GROUP_NAME_SERVER2",'127.0.0.1', SERVER_MYPORT_4, '', 80, 60)
102 The UDF asynchronous_connection_failover_add_managed() executed successfully.
103
104 # 8. Verify replication_asynchronous_connection_failover on
105 # server1 has two rows and member action configuration version
106 # value for replication_asynchronous_connection_failover
107 # and for replication_asynchronous_connection_failover_managed.
108 # And the channel 'ch1' is connected to server3.
109
110
111 # 9. Verify replication_asynchronous_connection_failover on
112 # server2 has two rows and member action configuration version
113 # value for replication_asynchronous_connection_failover
114 # and for replication_asynchronous_connection_failover_managed.
115
116 [connection server2]
117
118 # 10. Stop group replication on existing primary (server1), the new
119 # primary will establish asynchronous replication channel (ch1)
120 # connection with sender which is server3.
121 # And the channel 'ch1' is connected to server3.
122
123 [connection server1]
124 include/stop_group_replication.inc
125 [connection server2]
126 include/gr_wait_primary_member_uuid.inc
127
128 # 11. Delete replication connection details for managed channel ch1
129 # from replication_asynchronous_connection_failover_managed
130 # and replication_asynchronous_connection_failover table
131 # through asynchronous_connection_failover_delete_managed() UDF.
132
133 [connection server2]
134 SELECT asynchronous_connection_failover_delete_managed('ch1', 'GROUP_NAME_SERVER2');
135 asynchronous_connection_failover_delete_managed('ch1', 'GROUP_NAME_SERVER2')
136 The UDF asynchronous_connection_failover_delete_managed() executed successfully.
137
138 # 12. Verify replication_asynchronous_connection_failover on
139 # server2 is empty and member action configuration version
140 # value for replication_asynchronous_connection_failover
141 # and for replication_asynchronous_connection_failover_managed.
142 # And the channel 'ch1' is connected to server3.
143
144 [connection server2]
145 #
146 # 13. Clean up.
147 #
148 [connection server1]
149 include/rpl_reset_slave.inc
150 [connection server2]
151 include/stop_slave.inc [FOR CHANNEL 'ch1']
152 include/rpl_reset_slave.inc
153 [connection server4]
154 include/stop_group_replication.inc
155 [connection server3]
156 include/stop_group_replication.inc
157 [connection server2]
158 include/stop_group_replication.inc
159 include/group_replication_end.inc