1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
|
include/group_replication.inc [rpl_server_count=4]
Warnings:
Note #### Sending passwords in plain text without SSL/TLS is extremely insecure.
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.
[connection server1]
# 1. Bootstrap GR on server1. Join server2 and server3
[connection server1]
SET GLOBAL group_replication_member_expel_timeout = 3600;
include/start_and_bootstrap_group_replication.inc
[connection server2]
SET GLOBAL group_replication_member_expel_timeout = 3600;
include/start_group_replication.inc
[connection server3]
SET GLOBAL group_replication_member_expel_timeout = 3600;
include/start_group_replication.inc
# 2. Kill server1.
# Server will return without starting Group Replication.
[connection server1]
# Kill and restart
include/rpl_reconnect.inc
[connection server2]
include/gr_wait_for_member_state.inc
[connection server3]
include/gr_wait_for_member_state.inc
# 3. Create and start the managed channel connected to server1.
[connection server4]
SELECT asynchronous_connection_failover_add_managed('ch2_4', 'GroupReplication', 'FAILOVER_GROUP_NAME', '127.0.0.1', SERVER_MYPORT_2, '', 60, 80);;
asynchronous_connection_failover_add_managed('ch2_4', 'GroupReplication', 'FAILOVER_GROUP_NAME', '127.0.0.1', SERVER_MYPORT_2, '', 60, 80)
The UDF asynchronous_connection_failover_add_managed() executed successfully.
CHANGE REPLICATION SOURCE TO SOURCE_HOST='127.0.0.1', SOURCE_USER='root', SOURCE_AUTO_POSITION=1, SOURCE_CONNECTION_AUTO_FAILOVER=1, SOURCE_PORT=SERVER_2_PORT, SOURCE_RETRY_COUNT=1, SOURCE_CONNECT_RETRY=1 FOR CHANNEL 'ch2_4';
Warnings:
Note 1759 Sending passwords in plain text without SSL/TLS is extremely insecure.
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.
include/start_slave.inc [FOR CHANNEL 'ch2_4']
# 4. Validate sender list has three possible connections
include/assert.inc ['There is a row in performance_schema.replication_asynchronous_connection_failover for server1']
# 5. Revert group_replication_member_expel_timeout to the
# default value on server2 and server3, which will cause
# server1 to be expelled.
[connection server2]
SET GLOBAL group_replication_member_expel_timeout = DEFAULT;
[connection server3]
SET GLOBAL group_replication_member_expel_timeout = DEFAULT;
# 6. server1 was removed from performance_schema.replication_asynchronous_connection_failover table.
[connection server4]
include/assert.inc ['There is no row in performance_schema.replication_asynchronous_connection_failover for server1']
# 7. Clean Up.
SET SESSION sql_log_bin = 0;
call mtr.add_suppression("The source .* for channel 'ch2_4' has joined the group .*, and so added its entry into replication_asynchronous_connection_failover table.");
call mtr.add_suppression("The Monitor IO thread detected that the source .* does not belong to the group majority, thence the channel .* will try to connect to another source.");
call mtr.add_suppression("The source .* for channel 'ch2_4' has left the group .*, and so removed its entry from replication_asynchronous_connection_failover table.");
call mtr.add_suppression("The group .* for the channel .* has been removed, and so removed its entry from replication_asynchronous_connection_failover_managed and all the group members from replication_asynchronous_connection_failover table.");
call mtr.add_suppression("The group .* for the channel .* has been added, and so added its entry in replication_asynchronous_connection_failover_managed and source to replication_asynchronous_connection_failover table.");
SET SESSION sql_log_bin = 1;
include/stop_slave.inc [FOR CHANNEL 'ch2_4']
include/rpl_reset_slave.inc
SELECT asynchronous_connection_failover_delete_managed('ch2_4', 'GROUP_NAME');
asynchronous_connection_failover_delete_managed('ch2_4', 'GROUP_NAME')
The UDF asynchronous_connection_failover_delete_managed() executed successfully.
[connection server1]
SET GLOBAL group_replication_member_expel_timeout = DEFAULT;
include/group_replication_end.inc
|
