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
|
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. Bootstrap M1. And create new users.
[connection server1]
include/start_and_bootstrap_group_replication.inc
SET SQL_LOG_BIN=0;
CREATE USER 'regular_user_p' IDENTIFIED BY 'password';
GRANT REPLICATION SLAVE ON *.* TO "regular_user_p";
SET SQL_LOG_BIN=1;
# 2. Reset recovery interval to 1 and count to 2 for M2.
[connection server2]
SET @saved_group_replication_recovery_reconnect_interval = @@GLOBAL.group_replication_recovery_reconnect_interval;
SET @saved_gr_recovery_retry_count = @@GLOBAL.group_replication_recovery_retry_count;
SET GLOBAL group_replication_recovery_reconnect_interval= 1;
SET GLOBAL group_replication_recovery_retry_count= 2;
SET GLOBAL group_replication_group_name= "GROUP_REPLICATION_GROUP_NAME";
# 3. Test START GR passing right credentials and wrong in channel.
CHANGE REPLICATION SOURCE TO SOURCE_USER= 'invalid', SOURCE_PASSWORD='wrong' FOR CHANNEL 'group_replication_recovery';
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.
START GROUP_REPLICATION USER='regular_user_p', PASSWORD='password';
include/gr_wait_for_member_state.inc
include/stop_group_replication.inc
# 4. Stop GR and check start GR does not work without credentials.
# Confirming credentials have been deleted.
START GROUP_REPLICATION;
include/gr_wait_for_member_state.inc
include/stop_group_replication.inc
# 5. Test START GR fails passing wrong credentials and right in channel.
CHANGE REPLICATION SOURCE TO SOURCE_USER= 'regular_user_p', SOURCE_PASSWORD='password' FOR CHANNEL 'group_replication_recovery';
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.
START GROUP_REPLICATION USER='user_wrong' , PASSWORD='password_wrong';
include/gr_wait_for_member_state.inc
include/stop_group_replication.inc
# 6. Start GR without credentials should work due to channel.
# Confirming credentials have been deleted.
include/start_group_replication.inc
include/stop_group_replication.inc
# 7. Cleanup.
CHANGE REPLICATION SOURCE TO SOURCE_USER = 'root' , SOURCE_PASSWORD = '' FOR CHANNEL 'group_replication_recovery';
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.
SET SESSION sql_log_bin = 0;
call mtr.add_suppression("Replica I/O for channel 'group_replication_recovery': Fatal error: Invalid .* username when attempting to connect to the source server.*");
call mtr.add_suppression("There was an error when connecting to the donor server. Please check that group_replication_recovery channel credentials and all MEMBER_HOST column values of performance_schema.replication_group_members table are correct and DNS resolvable.");
call mtr.add_suppression("For details please check performance_schema.replication_connection_status table and error log messages of Replica I/O for channel group_replication_recovery.");
call mtr.add_suppression("Maximum number of retries when trying to connect to a donor reached. Aborting group replication incremental recovery.");
call mtr.add_suppression("Fatal error during the incremental recovery process of Group Replication. The server will leave the group.");
call mtr.add_suppression("The server was automatically set into read only mode after an error was detected.");
call mtr.add_suppression("Skipping leave operation: concurrent attempt to leave the group is on-going.");
call mtr.add_suppression("The server was automatically set into read only mode after an error was detected.");
SET SESSION sql_log_bin = 1;
SET @@GLOBAL.group_replication_recovery_reconnect_interval = @saved_group_replication_recovery_reconnect_interval;
SET @@GLOBAL.group_replication_recovery_retry_count = @saved_gr_recovery_retry_count;
[connection server1]
SET SQL_LOG_BIN=0;
DROP USER 'regular_user_p';
SET SQL_LOG_BIN=1;
include/group_replication_end.inc
|
