-
Notifications
You must be signed in to change notification settings - Fork 4k
/
Copy pathgr_acf_receiver_group.result
58 lines (51 loc) · 3.31 KB
/
gr_acf_receiver_group.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
include/group_replication.inc
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 1 member group A in single-primary mode.
[connection server1]
include/start_and_bootstrap_group_replication.inc
############################################################
# 2. Deploy a 1 member group B in single-primary mode.
[connection server2]
include/start_and_bootstrap_group_replication.inc
############################################################
# 3. Configure replica to manage the asynchronous connection
# between group A (source) and group B (replica).
[connection server2]
SELECT asynchronous_connection_failover_add_managed('ch1', 'GroupReplication', 'GROUP_A', '127.0.0.1', SERVER_MYPORT_1, '', 90, 70);;
asynchronous_connection_failover_add_managed('ch1', 'GroupReplication', 'GROUP_A', '127.0.0.1', SERVER_MYPORT_1, '', 90, 70)
The UDF asynchronous_connection_failover_add_managed() executed successfully.
include/assert.inc ['There is one row in performance_schema.replication_asynchronous_connection_failover for server1']
include/assert.inc ['There is one row in performance_schema.replication_asynchronous_connection_failover_managed for group A']
############################################################
# 4. Create and start the managed channel.
[connection server2]
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_1_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/rpl/start_replica.inc [FOR CHANNEL 'ch1']
include/assert.inc [Verify channel ch1 IO_THREAD is ON and connected to server1]
include/assert.inc [Verify replica_monitor thread is running]
############################################################
# 5. Stop group replication on group B
# Channel ch1, and the Monitor IO thread started by it,
# will automatically be stopped.
[connection server2]
include/stop_group_replication.inc
include/assert.inc ['channel ch1 SQL_THREAD is OFF']
include/assert.inc ['channel ch1 IO_THREAD is OFF']
include/assert.inc ['replica_monitor thread is not running']
############################################################
# 6. Clean up.
[connection server2]
include/rpl/reset_replica.inc
SELECT asynchronous_connection_failover_delete_managed('ch1', 'GROUP_A');
asynchronous_connection_failover_delete_managed('ch1', 'GROUP_A')
The UDF asynchronous_connection_failover_delete_managed() executed successfully.
[connection server1]
include/stop_group_replication.inc
include/group_replication_end.inc