-
Notifications
You must be signed in to change notification settings - Fork 4k
/
Copy pathgr_acf_receiver_reset_channel.result
91 lines (84 loc) · 5.37 KB
/
gr_acf_receiver_reset_channel.result
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
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
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. Deploy a group in single-primary mode on server1 and server2.
[connection server1]
include/start_and_bootstrap_group_replication.inc
include/gr_assert_primary_member.inc
[connection server2]
CHANGE REPLICATION SOURCE TO SOURCE_HOST='127.0.0.1', SOURCE_USER='root', SOURCE_AUTO_POSITION=1, SOURCE_CONNECTION_AUTO_FAILOVER=0, SOURCE_PORT=SERVER_4_PORT, SOURCE_CONNECT_RETRY=1, SOURCE_RETRY_COUNT=1 FOR CHANNEL 'ch1';
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_group_replication.inc
include/gr_assert_secondary_member.inc
############################################################
# 2. Configure and start a failover channel on server1 that
# replicates from server4.
[connection server4]
[connection server1]
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_4_PORT, SOURCE_CONNECT_RETRY=1, SOURCE_RETRY_COUNT=1 FOR CHANNEL 'ch1';
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.
SELECT asynchronous_connection_failover_add_source('ch1', '127.0.0.1', SERVER_MYPORT_4, '', 50);;
asynchronous_connection_failover_add_source('ch1', '127.0.0.1', SERVER_MYPORT_4, '', 50)
The UDF asynchronous_connection_failover_add_source() executed successfully.
include/rpl/start_replica.inc [FOR CHANNEL 'ch1']
############################################################
# 3. Validate server1 and server2 configuration.
[connection server1]
include/assert.inc ['There is 1 row in performance_schema.replication_asynchronous_connection_failover']
include/assert.inc ['The version of replication_asynchronous_connection_failover must be 1']
include/assert.inc ['SOURCE_CONNECTION_AUTO_FAILOVER must be enabled on ch1']
include/assert.inc [Verify channel ch1 IO_THREAD is ON and connected to server4]
include/assert.inc [Verify channel ch1 SQL_THREAD is ON]
include/assert.inc [Verify replica_monitor thread is running]
[connection server2]
include/assert.inc ['The version of replication_asynchronous_connection_failover must be 1']
include/assert.inc ['SOURCE_CONNECTION_AUTO_FAILOVER must be enabled on ch1']
include/assert.inc [Verify channel ch1 IO_THREAD is OFF]
include/assert.inc [Verify channel ch1 SQL_THREAD is OFF]
include/assert.inc [Verify replica_monitor thread is not running]
############################################################
# 4. Stop and delete channel 'ch1' on server1 and server2.
[connection server2]
include/rpl/reset_replica.inc
[connection server1]
include/rpl/stop_replica.inc [FOR CHANNEL 'ch1']
include/rpl/reset_replica.inc
SELECT asynchronous_connection_failover_delete_source('ch1', '127.0.0.1', SERVER_MYPORT_4, '');;
asynchronous_connection_failover_delete_source('ch1', '127.0.0.1', SERVER_MYPORT_4, '')
The UDF asynchronous_connection_failover_delete_source() executed successfully.
############################################################
# 5. Validate server1 and server2 configuration.
[connection server1]
include/assert.inc ['There are 0 rows in performance_schema.replication_asynchronous_connection_failover']
include/assert.inc ['The version of replication_asynchronous_connection_failover must be 2']
include/assert.inc ['Verify ch1 was deleted']
include/assert.inc [Verify replica_monitor thread is not running]
[connection server2]
include/assert.inc ['The version of replication_asynchronous_connection_failover must be 2']
include/assert.inc ['Verify ch1 was deleted']
include/assert.inc [Verify replica_monitor thread is not running]
############################################################
# 6. Add server3 to the group.
[connection server3]
include/start_group_replication.inc
include/gr_assert_secondary_member.inc
include/assert.inc ['There are 0 rows in performance_schema.replication_asynchronous_connection_failover']
include/assert.inc ['The version of replication_asynchronous_connection_failover must be 2']
include/assert.inc ['Verify ch1 does noet exist']
include/assert.inc [Verify replica_monitor thread is not running]
############################################################
# 7. Clean up.
[connection server3]
include/stop_group_replication.inc
[connection server2]
include/stop_group_replication.inc
[connection server1]
include/stop_group_replication.inc
include/group_replication_end.inc